Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
@ 2019-06-24 14:43 ` bugzilla-daemon
  2019-06-24 17:12 ` bugzilla-daemon
                   ` (10 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-24 14:43 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

raestloz@posteo.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |raestloz@posteo.net

--- Comment #29 from raestloz@posteo.net ---
I'm having the same problem here, kernel 4.20.17. 
btmon shows error at Delete Stored Link Key with hciconfig hci0 up, unsupported
feature

based on https://bugzilla.kernel.org/show_bug.cgi?id=103451 it seems that my
dongle is also a fake (mismatch between bcdDevice and LMP subversion), but with
bcdDevice 88.91, which isn't covered by the kernel (currently covers 1.00 and
1.34)

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
  2019-06-24 14:43 ` [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable bugzilla-daemon
@ 2019-06-24 17:12 ` bugzilla-daemon
  2019-06-25 16:15 ` bugzilla-daemon
                   ` (9 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-24 17:12 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #30 from raestloz@posteo.net ---
Well, I tried to build a custom kernel (4.19.55) with my bcdDevice and LMP
subversion included in the btusb.c file. 

btmon shows promise, hcitool dev actually shows a device, but dmesg | grep
tooth reveals that I'm stuck at HCI_OP_READ_LOCAL_VERSION, apparently it times
out, reading hci0: command 0x1001 tx timeout and CSR: Local version failed
(-110)

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
  2019-06-24 14:43 ` [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable bugzilla-daemon
  2019-06-24 17:12 ` bugzilla-daemon
@ 2019-06-25 16:15 ` bugzilla-daemon
  2019-08-01  1:56 ` bugzilla-daemon
                   ` (8 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-06-25 16:15 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #31 from raestloz@posteo.net ---
After resetting btusb driver with sudo modprobe -r btusb and sudo modprobe
btusb, I can confirm that the bluetooth dongle is working

What I had to do was add bcdDevice 0x8891 and lmp_subver 0x0811 to the quirk
related functions. Inquiry command 0x1001 still timeouts, which necessitates
the forced driver load, but once it loads it works

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (2 preceding siblings ...)
  2019-06-25 16:15 ` bugzilla-daemon
@ 2019-08-01  1:56 ` bugzilla-daemon
  2019-08-15  5:54 ` bugzilla-daemon
                   ` (7 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-01  1:56 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

barfin@protonmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barfin@protonmail.com

--- Comment #32 from barfin@protonmail.com ---
(In reply to raestloz from comment #31)
> After resetting btusb driver with sudo modprobe -r btusb and sudo modprobe
> btusb, I can confirm that the bluetooth dongle is working
> 
> What I had to do was add bcdDevice 0x8891 and lmp_subver 0x0811 to the quirk
> related functions. Inquiry command 0x1001 still timeouts, which necessitates
> the forced driver load, but once it loads it works

i have this problem in kernel 5.2.5 :(

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (3 preceding siblings ...)
  2019-08-01  1:56 ` bugzilla-daemon
@ 2019-08-15  5:54 ` bugzilla-daemon
  2019-08-17  4:52 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-15  5:54 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

Arthur Fragoso (arthur@life.net.br) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arthur@life.net.br

--- Comment #33 from Arthur Fragoso (arthur@life.net.br) ---
Same here:

0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode).

But the product name is: JL AC69 A10

I tested in Linux 5.2.8-1-MANJARO, and the 4.19.57-1-MANJARO.

The problems are:

- After booting up the OS with the BT Dongle in, if I try to 'sudo bluetoothctl
power on', it fails and 'btmon' returns this:


@ MGMT Command: Set Powered (0x0005) plen 1                                    
         {0x0001} [hci0] 34.681295
        Powered: Enabled (0x01)
= Open Index: 00:1A:7D:DA:71:10                                                
                  [hci0] 34.743182
< HCI Command: Reset (0x03|0x0003) plen 0                                      
               #2 [hci0] 34.743412
= Close Index: 00:1A:7D:DA:71:10                                               
                  [hci0] 44.768939
@ MGMT Event: Command Status (0x0002) plen 3                                   
         {0x0001} [hci0] 44.772086
      Set Powered (0x0005)
        Status: Failed (0x03)
= bluetoothd: Failed to set mode: Failed (0x03)                                
                  [hci0] 44.790305


If I unplug and plug it back, the power on command will work fine. If it is set
to AutoEnable on /etc/bluetooth/main.conf, it will also be powered up after
plugin it back.
If I power off, it will only work again if I unplug and plug it back. So it's
not a big problem.


The big deal is that I can't make it to scan:

$ sudo bluetoothctl scan on

bluetoothd[2358]: src/adapter.c:start_discovery() sender :1.268
bluetoothd[2358]: src/adapter.c:update_discovery_filter() 
bluetoothd[2358]: src/adapter.c:discovery_filter_to_mgmt_cp() 
bluetoothd[2358]: src/adapter.c:trigger_start_discovery() 
bluetoothd[2358]: src/adapter.c:cancel_passive_scanning() 
bluetoothd[2358]: src/adapter.c:start_discovery_timeout() 
bluetoothd[2358]: src/adapter.c:start_discovery_timeout()
adapter->current_discovery_filter == 0
bluetoothd[2358]: src/adapter.c:start_discovery_complete() status 0x03


@ MGMT Command: Start Discovery (0x0023) plen 1           {0x0001} [hci0]
37.252439
        Address type: 0x07
          BR/EDR
          LE Public
          LE Random
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6      #81 [hci0]
37.252583
        Address: 06:4D:6A:64:58:36 (Non-Resolvable)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7     #82 [hci0]
39.423752
        Type: Active (0x01)
        Interval: 22.500 msec (0x0024)
        Window: 11.250 msec (0x0012)
        Own address type: Random (0x01)
        Filter policy: Accept all advertisement (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4            {0x0001} [hci0]
39.423747
      Start Discovery (0x0023) plen 1
        Status: Failed (0x03)
        Address type: 0x07
          BR/EDR
          LE Public
          LE Random
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2         #83 [hci0]
41.557120
        Scanning: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
< HCI Command: Inquiry (0x01|0x0001) plen 5                    #84 [hci0]
43.690407
        Access code: 0x9e8b33 (General Inquiry)
        Length: 10.24s (0x08)
        Num responses: 0


I will try to apply the patch and compile the kernel to see if I can get it to
work. It's crazy to think this thread started in November 2013, and currently
there are many of those CSR dongles being sold.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (4 preceding siblings ...)
  2019-08-15  5:54 ` bugzilla-daemon
@ 2019-08-17  4:52 ` bugzilla-daemon
  2019-08-17 22:42 ` bugzilla-daemon
                   ` (5 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-17  4:52 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

Sergey Kondakov (virtuousfox@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |virtuousfox@gmail.com

--- Comment #34 from Sergey Kondakov (virtuousfox@gmail.com) ---
(In reply to Arthur Fragoso from comment #33)
> Same here:
> 
> 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode).
> 
> But the product name is: JL AC69 A10
> 
> I tested in Linux 5.2.8-1-MANJARO, and the 4.19.57-1-MANJARO.
> 
> The problems are:
> 
> - After booting up the OS with the BT Dongle in, if I try to 'sudo
> bluetoothctl power on', it fails and 'btmon' returns this:
> ...
> I will try to apply the patch and compile the kernel to see if I can get it
> to work. It's crazy to think this thread started in November 2013, and
> currently there are many of those CSR dongles being sold.

At least it somehow works for you ! I just recently got one in attempt to
"upgrade" from 2.1 to 4.0 (also 0a12:0001) and have a spare for my Sony
DualShocks 3&4. It works under Windows but I don't actually remember if I
managed to successfully test it under Linux. Under kernel 5.2.8 bluez acts if
it wasn't there but in reality it fails with this ridiculous "Delete Stored
Link Key: Unsupported Feature or Parameter Value". btusb does not have 'quirks'
option and adding 'quirks=0a12:0001:HCI_QUIRK_BROKEN_STORED_LINK_KEY' to
usbcore doesn't seem to be doing anything.

But neither you or me are going to use that patch because BT stack was
completely rewritten and its logic is completely different now. If developers
don't want to ignore failures to initiate such "important" optional functions
and enable quirks automatically on pre-init sanity check then at least someone
could have said somewhere how to enable the damn things at runtime without
hard-coding IDs of your random noname dongles into kernel's code…

How the hell people are using those BT quirks ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (5 preceding siblings ...)
  2019-08-17  4:52 ` bugzilla-daemon
@ 2019-08-17 22:42 ` bugzilla-daemon
  2019-08-18  1:45 ` bugzilla-daemon
                   ` (4 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-17 22:42 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #35 from Arthur Fragoso (arthur@life.net.br) ---

The code for these devices are bellow.

You are right, the patch is way too old for this.

I will probably buy a different device while we wait for someone with more
knowledge to fix this.


/linux/drivers/bluetooth/btusb.c

kenel 5.2.8

static const struct usb_device_id blacklist_table[] = {
        /* CSR BlueCore devices */
        { USB_DEVICE(0x0a12, 0x0001), .driver_info = BTUSB_CSR },


static int btusb_setup_csr(struct hci_dev *hdev)
{
        struct hci_rp_read_local_version *rp;
        struct sk_buff *skb;

        BT_DBG("%s", hdev->name);

        skb = __hci_cmd_sync(hdev, HCI_OP_READ_LOCAL_VERSION, 0, NULL,
                             HCI_INIT_TIMEOUT);
        if (IS_ERR(skb)) {
                int err = PTR_ERR(skb);
                bt_dev_err(hdev, "CSR: Local version failed (%d)", err);
                return err;
        }

        if (skb->len != sizeof(struct hci_rp_read_local_version)) {
                bt_dev_err(hdev, "CSR: Local version length mismatch");
                kfree_skb(skb);
                return -EIO;
        }

        rp = (struct hci_rp_read_local_version *)skb->data;

        /* Detect controllers which aren't real CSR ones. */
        if (le16_to_cpu(rp->manufacturer) != 10 ||
            le16_to_cpu(rp->lmp_subver) == 0x0c5c) {
                /* Clear the reset quirk since this is not an actual
                 * early Bluetooth 1.1 device from CSR.
                 */
                clear_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);

                /* These fake CSR controllers have all a broken
                 * stored link key handling and so just disable it.
                 */
                set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY, &hdev->quirks);
        }

        kfree_skb(skb);

        return 0;
}

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (6 preceding siblings ...)
  2019-08-17 22:42 ` bugzilla-daemon
@ 2019-08-18  1:45 ` bugzilla-daemon
  2019-08-20  4:49 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-18  1:45 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #36 from Sergey Kondakov (virtuousfox@gmail.com) ---
(In reply to Arthur Fragoso from comment #35)
> The code for these devices are bellow.
> 
> You are right, the patch is way too old for this.
> 
> I will probably buy a different device while we wait for someone with more
> knowledge to fix this.
>...
>       /* Detect controllers which aren't real CSR ones. */
>       if (le16_to_cpu(rp->manufacturer) != 10 ||
>           le16_to_cpu(rp->lmp_subver) == 0x0c5c) {
>...

Luckily, I still have my old 2.1 dongle.

It seems that this check is too specific, mine has 0x811 subversion but the
real problem is idiotic notion of holding all BT devices to some imaginary
standard of compliant vendor-approved behaviour and creating blacklists for
actual devices only if someone from BT maintainers have heard something about
some problems from someone. No normal user is going to write them letter with
complains, let alone patches for hard-coded workarounds to artificial problems.
They need to redo the whole initialization logic to be more generic or at least
allow passing quirk-flags at runtime.

There is and will be myriad of devices with random IDs and crappy firmwares,
sometimes even circuitry, and kernel MUST make all that crap work at least
partially, not backdown on smallest of mislabelings. It is saddening to see
only recently created built-in Windows 10 BT stack to behave more sanely than
bluez.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (7 preceding siblings ...)
  2019-08-18  1:45 ` bugzilla-daemon
@ 2019-08-20  4:49 ` bugzilla-daemon
  2019-09-11 18:20 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-08-20  4:49 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #37 from Sergey Kondakov (virtuousfox@gmail.com) ---
Created attachment 284525
  --> https://bugzilla.kernel.org/attachment.cgi?id=284525&action=edit
patches.hsf/btusb-Enablement-of-HCI_QUIRK_BROKEN_STORED_LINK_KEY-quirk.patch

Made the patch based on raestloz's comments for our
bcdDevice=88.91/LMP_sv=0x811 CSR 4.0 device to enable crutches that make the
stack eat it up.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (8 preceding siblings ...)
  2019-08-20  4:49 ` bugzilla-daemon
@ 2019-09-11 18:20 ` bugzilla-daemon
  2019-09-16  7:30 ` bugzilla-daemon
  2019-09-16 11:12 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-11 18:20 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

pires.carvalho@gmail.com (pires.carvalho@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pires.carvalho@gmail.com

--- Comment #38 from pires.carvalho@gmail.com (pires.carvalho@gmail.com) ---
Hi,

I merged a few fixes and quirks (including some from this thread) and sent them
to linux-bluetooth@vger.kernel.org :

https://www.spinics.net/lists/linux-bluetooth/msg81304.html

Feel free to test it if you have a simillar CSR device
(ATTRS{idVendor}=="0a12", ATTRS{idProduct}=="0001", ATTRS{bcdDevice}=="8891").

It's not perfect, but it allows the use of the adapter and connect a headset
(with some connect errors/retries now and then).

Regards.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (9 preceding siblings ...)
  2019-09-11 18:20 ` bugzilla-daemon
@ 2019-09-16  7:30 ` bugzilla-daemon
  2019-09-16 11:12 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-16  7:30 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #39 from Sergey Kondakov (virtuousfox@gmail.com) ---
(In reply to Fernando Carvalho from comment #38)
> Hi,
> 
> I merged a few fixes and quirks (including some from this thread) and sent
> them to linux-bluetooth@vger.kernel.org :
> 
> https://www.spinics.net/lists/linux-bluetooth/msg81304.html
> 
> Feel free to test it if you have a simillar CSR device
> (ATTRS{idVendor}=="0a12", ATTRS{idProduct}=="0001",
> ATTRS{bcdDevice}=="8891").
> 
> It's not perfect, but it allows the use of the adapter and connect a headset
> (with some connect errors/retries now and then).
> 
> Regards.

Great work ! Unlike the actual maintainers who don't even bother to read
bug-tracker anymore or use ready fixes for their code that they themselves
don't care about, it seems.

However, I doubt that even a scrupulous maintainer would ever allow that many
dedicated workaround options instead of one, in style of usbcore, usbhid and
snd-hda-intel even though they all use inconsistent schemes of their own. A
more reasonable approach would be passing model=vendorID:productID:<"model">
space-separated (to allow several dongles) override pairs with each having a
bunch of quirk-hacks associated (as snd-hda-intel) on it,
quirks=vendorID:productID:<comma separated list of all quirks> space-separated
pairs (as usbcore/usbhid) or both. But that means doing even more work that can
be ignored or offhandedly dismissed for code that was written without enough
foresight for it in the first place.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

* [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
       [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
                   ` (10 preceding siblings ...)
  2019-09-16  7:30 ` bugzilla-daemon
@ 2019-09-16 11:12 ` bugzilla-daemon
  11 siblings, 0 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-09-16 11:12 UTC (permalink / raw)
  To: linux-bluetooth

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #40 from raestloz@posteo.net ---
Windows 10 doesn't exhibit the same issues with the exact same dongle, so I
believe what they do is ignore the feature issues presented by dongles outright

I personally don't think it's good to do that, there's a reason standards
exist, so perhaps a better way is to move bluetooth driver out of kernel so
fixing the driver to account for device quirks doesn't mean recompiling the
entire kernel?

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, back to index

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
2019-06-24 14:43 ` [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable bugzilla-daemon
2019-06-24 17:12 ` bugzilla-daemon
2019-06-25 16:15 ` bugzilla-daemon
2019-08-01  1:56 ` bugzilla-daemon
2019-08-15  5:54 ` bugzilla-daemon
2019-08-17  4:52 ` bugzilla-daemon
2019-08-17 22:42 ` bugzilla-daemon
2019-08-18  1:45 ` bugzilla-daemon
2019-08-20  4:49 ` bugzilla-daemon
2019-09-11 18:20 ` bugzilla-daemon
2019-09-16  7:30 ` bugzilla-daemon
2019-09-16 11:12 ` bugzilla-daemon

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox