Eric Lee / smarc-fsl-linux-kernel

21 Dec, 2011

1 commit

28 Jun, 2011

1 commit

  • daf4ce85c   bluetooth: uses crypto interfaces, select CRYPTO ... Browse Code »

    Recent changes to hci_core.c use crypto interfaces, so select CRYPTO
    to make sure that those interfaces are present.

    Fixes these build errors when CRYPTO is not enabled:

    net/built-in.o: In function `hci_register_dev':
    (.text+0x4cf86): undefined reference to `crypto_alloc_base'
    net/built-in.o: In function `hci_unregister_dev':
    (.text+0x4f912): undefined reference to `crypto_destroy_tfm'

    Signed-off-by: Randy Dunlap
    Signed-off-by: John W. Linville

    Randy Dunlap
     

14 Jun, 2011

1 commit

  • 3a0259bb8   Bluetooth: Add support for using the crypto subsystem ... Browse Code »

    This will allow using the crypto subsystem for encrypting data. As SMP
    (Security Manager Protocol) is implemented almost entirely on the host
    side and the crypto module already implements the needed methods
    (AES-128), it makes sense to use it.

    There's now a new module option to enable/disable SMP support.

    Signed-off-by: Vinicius Costa Gomes
    Signed-off-by: Anderson Briglia
    Signed-off-by: Gustavo F. Padovan

    Vinicius Costa Gomes
     

01 Mar, 2011

1 commit

  • d45dcef77   Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig ... Browse Code »

    If we want something "bool" built-in in something "tristate" it can't
    "depend on" the tristate config option.

    Report by DaveM:

    I give it 'y' just to make it happen, for both, and afterways no
    matter how many times I rerun "make oldconfig" I keep seeing things
    like this in my build:

    scripts/kconfig/conf --silentoldconfig Kconfig
    include/config/auto.conf:986:warning: symbol value 'm' invalid for BT_SCO
    include/config/auto.conf:3156:warning: symbol value 'm' invalid for BT_L2CAP

    Reported-by: David S. Miller
    Signed-off-by: Gustavo F. Padovan
    Signed-off-by: John W. Linville

    Gustavo F. Padovan
     

15 Feb, 2011

1 commit

  • 642745184   Bluetooth: Merge L2CAP and SCO modules into bluetooth.ko ... Browse Code »

    Actually doesn't make sense have these modules built separately.
    The L2CAP layer is needed by almost all Bluetooth protocols and profiles.
    There isn't any real use case without having L2CAP loaded.
    SCO is only essential for Audio transfers, but it is so small that we can
    have it loaded always in bluetooth.ko without problems.
    If you really doesn't want it you can disable SCO in the kernel config.

    Signed-off-by: Gustavo F. Padovan

    Gustavo F. Padovan
     

08 Feb, 2011

1 commit

22 Jul, 2010

1 commit

10 May, 2010

1 commit

  • 84fb0a633   Bluetooth: Add Kconfig option for L2CAP Extended Features ... Browse Code »

    The L2CAP Extended Features are still unstable and under development,
    so we are adding them under the EXPERIMENTAL flag to get more feedback
    on them. L2CAP Extended Features includes the Enhanced Retransmission
    and Streaming Modes, Frame Check Sequence (FCS), and Segmentation and
    Reassemby (SAR).

    Signed-off-by: Gustavo F. Padovan
    Reviewed-by: João Paulo Rechi Vita
    Signed-off-by: Marcel Holtmann

    Gustavo F. Padovan
     

25 Aug, 2009

1 commit

  • cbe86b98a   Bluetooth: Add missing selection of CONFIG_CRC16 for L2CAP layer ... Browse Code »

    Fix net/bluetooth/l2cap.c build errors:

    l2cap.c:(.text+0x126035): undefined reference to `crc16'
    l2cap.c:(.text+0x126323): undefined reference to `crc16'
    l2cap.c:(.text+0x12668e): undefined reference to `crc16'
    l2cap.c:(.text+0x12683b): undefined reference to `crc16'
    l2cap.c:(.text+0x126956): undefined reference to `crc16'
    net/built-in.o:l2cap.c:(.text+0x129041): more undefined references to `crc16' follow

    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Marcel Holtmann

    Randy Dunlap
     

14 Jun, 2009

1 commit

10 May, 2007

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds