<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>37bac77e - Bluetooth: hci_uart: Add support for Amlogic HCI UART</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#37bac77e</link>
        <description>Bluetooth: hci_uart: Add support for Amlogic HCI UARTAdd a new HCI protocol HCI_UART_AML for the Amlogic Bluetoothcontroller. It works on the standard H4 protocol via a 4-wire UARTinterface, with baud rates up to 4 Mbps.The controller supports two types of commands: the TCI commands and thevendor command. The former is for initial setup including setting baudrates, downloading fw, starting chip and etc, while the latter is fordumping firmware versions and setting public address after firmwareupdates and normal startup.It was verified on board of T602 (S905X4 + W265S2).dmesg:..[    5.313450] Bluetooth: HCI UART protocol AML registered[    6.506052] Bluetooth: hci0: fw_version: date = 42.28, number = 0xb2fd...Co-developed-by: Ye He &lt;ye.he@amlogic.com&gt;Signed-off-by: Ye He &lt;ye.he@amlogic.com&gt;Signed-off-by: Yang Li &lt;yang.li@amlogic.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Fri, 09 Aug 2024 05:42:25 +0000</pubDate>
        <dc:creator>Yang Li &lt;yang.li@amlogic.com&gt;</dc:creator>
    </item>
<item>
        <title>c2b636b3 - Bluetooth: btintel_pcie: Add support for PCIe transport</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#c2b636b3</link>
        <description>Bluetooth: btintel_pcie: Add support for PCIe transportAdd initial code to support Intel bluetooth devices based on PCIetransport. Allocate memory for TX &amp; RX buffers, internal structures,initialize interrupts for TX &amp; RX and PCIe device.Signed-off-by: Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;Suggested-by: Bjorn Helgaas &lt;helgaas@kernel.org&gt;Suggested-by: Paul Menzel &lt;pmenzel@molgen.mpg.de&gt;Signed-off-by: Kiran K &lt;kiran.k@intel.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Tue, 07 May 2024 15:56:57 +0000</pubDate>
        <dc:creator>Tedd Ho-Jeong An &lt;tedd.an@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>689ca16e - Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#689ca16e</link>
        <description>Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsetsThis adds a driver based on serdev driver for the NXP BT serial protocolbased on running H:4, which can enable the built-in Bluetooth deviceinside an NXP BT chip.This driver has Power Save feature that will put the chip into sleep statewhenever there is no activity for 2000ms, and will be woken up when anyactivity is to be initiated over UART.This driver enables the power save feature by default by sending the vendorspecific commands to the chip during setup.During setup, the driver checks if a FW is already running on the chipby waiting for the bootloader signature, and downloads device specific FWfile into the chip over UART if bootloader signature is received..Signed-off-by: Neeraj Sanjay Kale &lt;neeraj.sanjaykale@nxp.com&gt;Reviewed-by: Ilpo J&#228;rvinen &lt;ilpo.jarvinen@linux.intel.com&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Thu, 16 Mar 2023 17:22:14 +0000</pubDate>
        <dc:creator>Neeraj Sanjay Kale &lt;neeraj.sanjaykale@nxp.com&gt;</dc:creator>
    </item>
<item>
        <title>8a061276 - Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCIe boards</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#8a061276</link>
        <description>Bluetooth: hci_bcm4377: Add new driver for BCM4377 PCIe boardsBroadcom BCM4377/4378/4387 are dual WiFi/Bluetooth boards found in Applemachines. This driver adds support for the Bluetooth function whichexposes a shared memory IPC protocol over PCIe to tunnel HCI traffic.Signed-off-by: Sven Peter &lt;sven@svenpeter.dev&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Fri, 04 Nov 2022 21:13:03 +0000</pubDate>
        <dc:creator>Sven Peter &lt;sven@svenpeter.dev&gt;</dc:creator>
    </item>
<item>
        <title>8c0d17b6 - Bluetooth: mediatek: add BT_MTK module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#8c0d17b6</link>
        <description>Bluetooth: mediatek: add BT_MTK moduleAdd BT_MTK module that is a preliminary patch to introduce mt7921s supportto share the logic betweem btusb and btmtksdio.Signed-off-by: Sean Wang &lt;sean.wang@mediatek.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Mon, 18 Oct 2021 21:30:12 +0000</pubDate>
        <dc:creator>Sean Wang &lt;sean.wang@mediatek.com&gt;</dc:creator>
    </item>
<item>
        <title>afd2daa2 - Bluetooth: Add support for virtio transport driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#afd2daa2</link>
        <description>Bluetooth: Add support for virtio transport driverThis adds support for Bluetooth HCI transport over virtio.Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: Luiz Augusto von Dentz &lt;luiz.von.dentz@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Tue, 06 Apr 2021 19:55:53 +0000</pubDate>
        <dc:creator>Marcel Holtmann &lt;marcel@holtmann.org&gt;</dc:creator>
    </item>
<item>
        <title>54976bc7 - Bluetooth: btwilink: drop superseded driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#54976bc7</link>
        <description>Bluetooth: btwilink: drop superseded driverAll users of this driver have been converted to the serdev basedhci_ll driver. The unused driver can be safely dropped now.Signed-off-by: Sebastian Reichel &lt;sebastian.reichel@collabora.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Thu, 03 Oct 2019 13:41:47 +0000</pubDate>
        <dc:creator>Sebastian Reichel &lt;sebastian.reichel@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>9aebfd4a - Bluetooth: mediatek: add support for MediaTek MT7663S and MT7668S SDIO devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#9aebfd4a</link>
        <description>Bluetooth: mediatek: add support for MediaTek MT7663S and MT7668S SDIO devicesThis adds the support of enabling MT7663S and MT7668S SDIO-basedBluetooth function.There are quite many differences between MT766[3,8]S and standardBluetooth SDIO devices such as Type-A and Type-B devices. For example,MT766[3,8]S have its own SDIO registers layout, definition, SDIO packetformat, and the specific flow should be programmed on them to completethe device initialization and low power control and so on.Currently, there are many independent programming sequences from thetransport which are exactly the same as the ones in btusb.c about MediaTeksupport [1] and btmtkuart.c. We can try to split the transport independentBluetooth setups on the advance, place them into the common files and allowvarous transport drivers to reuse them in the future.[1] http://lists.infradead.org/pipermail/linux-mediatek/2019-January/017074.htmlSigned-off-by: Sean Wang &lt;sean.wang@mediatek.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Fri, 08 Mar 2019 01:15:44 +0000</pubDate>
        <dc:creator>Sean Wang &lt;sean.wang@mediatek.com&gt;</dc:creator>
    </item>
<item>
        <title>7237c4c9 - Bluetooth: mediatek: Add protocol support for MediaTek serial devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#7237c4c9</link>
        <description>Bluetooth: mediatek: Add protocol support for MediaTek serial devicesThis adds a driver based on serdev driver for the MediaTek serial protocolbased on running H:4, which can enable the built-in Bluetooth device insideMT7622 SoC.Signed-off-by: Sean Wang &lt;sean.wang@mediatek.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Tue, 07 Aug 2018 17:52:48 +0000</pubDate>
        <dc:creator>Sean Wang &lt;sean.wang@mediatek.com&gt;</dc:creator>
    </item>
<item>
        <title>6f6f1ece - Bluetooth: Remove unused btuart_cs driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#6f6f1ece</link>
        <description>Bluetooth: Remove unused btuart_cs driverWith patch 279c936153199 the btuart_cs driver has been deprecated infavor of serial_cs + hci_uart combination.  static struct pcmcia_device_id btuart_ids[] = {         /* don&apos;t use this driver. Use serial_cs + hci_uart instead */         PCMCIA_DEVICE_NULL  };Intead of keeping it around, just remove it since it is not evenassigned to any PCMCIA identifiers anymore.Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Sat, 24 Mar 2018 09:19:54 +0000</pubDate>
        <dc:creator>Marcel Holtmann &lt;marcel@holtmann.org&gt;</dc:creator>
    </item>
<item>
        <title>38aa4da5 - Bluetooth: btrsi: add new rsi bluetooth driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#38aa4da5</link>
        <description>Bluetooth: btrsi: add new rsi bluetooth driverRedpine bluetooth driver is a thin driver which depends on&apos;rsi_91x&apos; driver for transmitting and receiving packetsto/from device. It creates hci interface when attach() iscalled from &apos;rsi_91x&apos; module.Signed-off-by: Prameela Rani Garnepudi &lt;prameela.j04cs@gmail.com&gt;Signed-off-by: Siva Rebbagondla &lt;siva.rebbagondla@redpinesignals.com&gt;Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Reviewed-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: Amitkumar Karwar &lt;amit.karwar@redpinesignals.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Tue, 27 Feb 2018 14:26:15 +0000</pubDate>
        <dc:creator>Prameela Rani Garnepudi &lt;prameela.j04cs@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>1fb78fb6 - Bluetooth: try to improve CONFIG_SERIAL_DEV_BUS dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#1fb78fb6</link>
        <description>Bluetooth: try to improve CONFIG_SERIAL_DEV_BUS dependencyWith CONFIG_SERIAL_DEV_BUS=m, the hci_serdev.o file does not actuallyget built into hci_uart.o as the Makefile doesn&apos;t pick it up, leadingto a link error with anything referring to it:ERROR: &quot;hci_uart_register_device&quot; [drivers/bluetooth/hci_nokia.ko] undefined!scripts/Makefile.modpost:91: recipe for target &apos;__modpost&apos; failedChanging this in the Makefile would cause another problem whenhci_uart itself is built-in and cannot reference symbols from theserdev module.This tries to address both problems by introducing a new hiddenKconfig symbol that controls both the compilation of hci_serdev.oand whether the Nokia driver can be selected. This seems to addressthe problem for me, though there might be a better way to do it.Fixes: 7bb318680e86 (&quot;Bluetooth: add nokia driver&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Wed, 19 Apr 2017 17:50:18 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>7bb31868 - Bluetooth: add nokia driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#7bb31868</link>
        <description>Bluetooth: add nokia driverThis adds a driver for the Nokia H4+ protocol, which is usedat least on the Nokia N9, N900 &amp; N950.Signed-off-by: Sebastian Reichel &lt;sre@kernel.org&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Thu, 13 Apr 2017 00:26:59 +0000</pubDate>
        <dc:creator>Sebastian Reichel &lt;sre@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>82f5169b - Bluetooth: hci_uart: add serdev driver support library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#82f5169b</link>
        <description>Bluetooth: hci_uart: add serdev driver support libraryThis adds library functions for serdev based BT drivers. This is largelycopied from hci_ldisc.c and modified to use serdev calls. There&apos;s a littlebit of duplication, but I avoided intermixing this as the ldisc code shouldeventually go away.Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;Cc: Marcel Holtmann &lt;marcel@holtmann.org&gt;Cc: Gustavo Padovan &lt;gustavo@padovan.org&gt;Cc: Johan Hedberg &lt;johan.hedberg@gmail.com&gt;Cc: linux-bluetooth@vger.kernel.orgAcked-by: Pavel Machek &lt;pavel@ucw.cz&gt;[Fix style issues reported by Pavel]Signed-off-by: Sebastian Reichel &lt;sre@kernel.org&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Tue, 28 Mar 2017 15:59:35 +0000</pubDate>
        <dc:creator>Rob Herring &lt;robh@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>6bdf1e0e - Makefile: drop -D__CHECK_ENDIAN__ from cflags</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#6bdf1e0e</link>
        <description>Makefile: drop -D__CHECK_ENDIAN__ from cflagsThat&apos;s the default now, no need for makefiles to set it.Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Acked-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Acked-by: Marc Kleine-Budde &lt;mkl@pengutronix.de&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Arend van Spriel &lt;arend.vanspriel@broadcom.com&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Thu, 15 Dec 2016 02:07:46 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>162f812f - Bluetooth: hci_uart: Add Marvell support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#162f812f</link>
        <description>Bluetooth: hci_uart: Add Marvell supportThis patch introduces support for Marvell Bluetooth controller overUART (8897 for now). In order to send the final firmware at full speed,a helper firmware is firstly sent. Firmware download is driven by thecontroller which sends request firmware packets (including expectedsize).This driver is a global rework of the one proposed byAmitkumar Karwar &lt;akarwar@marvell.com&gt;.Signed-off-by: Loic Poulain &lt;loic.poulain@intel.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Mon, 19 Sep 2016 14:29:27 +0000</pubDate>
        <dc:creator>Loic Poulain &lt;loic.poulain@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>1511cc75 - Bluetooth: Introduce Qualcomm WCNSS SMD based HCI driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#1511cc75</link>
        <description>Bluetooth: Introduce Qualcomm WCNSS SMD based HCI driverThe Qualcomm WCNSS chip provides two SMD channels to the BT core; onefor command and one for event packets. This driver exposes the twochannels as a hci device.Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@sonymobile.com&gt;Signed-off-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Sat, 13 Aug 2016 00:01:28 +0000</pubDate>
        <dc:creator>Bjorn Andersson &lt;bjorn.andersson@sonymobile.com&gt;</dc:creator>
    </item>
<item>
        <title>395174bb - Bluetooth: hci_uart: Add Intel/AG6xx support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#395174bb</link>
        <description>Bluetooth: hci_uart: Add Intel/AG6xx supportThis driver implements support for iBT2.1 Bluetooth controller embeddedin the AG620 communication combo. The controller needs to be configuredwith bddata and can be patched with a binary patch file (pbn).These operations are performed in manufacturing mode.Signed-off-by: Loic Poulain &lt;loic.poulain@intel.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Mon, 22 Feb 2016 09:48:03 +0000</pubDate>
        <dc:creator>Loic Poulain &lt;loic.poulain@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0ff252c1 - Bluetooth: hciuart: Add support QCA chipset for UART</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/bluetooth/Makefile#0ff252c1</link>
        <description>Bluetooth: hciuart: Add support QCA chipset for UARTQCA61x4 chips have supported sleep feature using In-Band-Sleep commandsto enable sleep feature based on H4 protocol. After sendingpatch/nvm configuration is done, IBS mode will be up and runningSigned-off-by: Ben Young Tae Kim &lt;ytkim@qca.qualcomm.com&gt;Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;

            List of files:
            /linux-6.15/drivers/bluetooth/Makefile</description>
        <pubDate>Mon, 10 Aug 2015 21:24:17 +0000</pubDate>
        <dc:creator>Ben Young Tae Kim &lt;ytkim@qca.qualcomm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
