linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Danis <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 109321] New: ASUS T100TA Bluetooth stopped working
Date: Tue, 15 Dec 2015 17:37:02 +0100	[thread overview]
Message-ID: <567041AE.5060001@linux.intel.com> (raw)
In-Reply-To: <bug-109321-62941@https.bugzilla.kernel.org/>

Hello,

On 14/12/2015 02:36, bugzilla-daemon@bugzilla.kernel.org wrote:
> Hello
>
> since kernel 4.2.3 the bluetooth on ASUS t100TA stopped working
>
> can no longer initialize it using hciattach /dev/ttyS4 bcm43xx command it
> always times out it also registers different in dmesg
>
>   80860F0A:00: ttyS4 at MMIO 0x9094d000 (irq = 191, base_baud = 2764800) is a
> 16550A
> [    5.629222] Bluetooth: Core ver 2.21
> [    5.629287] NET: Registered protocol family 31
> [    5.629291] Bluetooth: HCI device and connection manager initialized
> [    5.629299] Bluetooth: HCI socket layer initialized
> [    5.629305] Bluetooth: L2CAP socket layer initialized
> [    5.629318] Bluetooth: SCO socket layer initialized
> [    5.643749] Bluetooth: HCI UART driver ver 2.3
> [    5.643757] Bluetooth: HCI UART protocol H4 registered
> [    5.643760] Bluetooth: HCI UART protocol BCSP registered
> [    5.643763] Bluetooth: HCI UART protocol LL registered
> [    5.643765] Bluetooth: HCI UART protocol ATH3K registered
> [    5.643768] Bluetooth: HCI UART protocol Three-wire (H5) registered
> [    5.643853] Bluetooth: HCI UART protocol Intel registered
> [    5.657970] hci_bcm BCM2E39:00: BCM irq: 192
> [    5.658046] Bluetooth: BCM2E39:00: Asus T100TA: Overwriting IRQ polarity to
> active low
> [    5.658051] hci_bcm BCM2E39:00: BCM2E39:00 device registered.
> [    5.658224] Bluetooth: HCI UART protocol BCM registered
>
> not sure if this is a bug in the kernel driver or if something was changed
> BlueZ and not updated in the bcm driver
>
> also it no longer registers with rfkill which i think was changed

Bluetooth BCM chipset is no more managed by rfkill and hciattach.
You should use btattach to register it (BlueZ >= 5.31):
	btattach --bredr /dev/ttyS4 -P bcm
then (you should change the device address):
	btmgmt public-addr "43:24:b3:01:02:03"

Hope this helps


  reply	other threads:[~2015-12-15 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  1:36 [Bug 109321] New: ASUS T100TA Bluetooth stopped working bugzilla-daemon
2015-12-15 16:37 ` Frederic Danis [this message]
2015-12-16 15:44 ` [Bug 109321] " bugzilla-daemon
2015-12-17  3:24 ` bugzilla-daemon
2016-03-01 23:34 ` bugzilla-daemon
2016-03-22  7:01 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=567041AE.5060001@linux.intel.com \
    --to=frederic.danis@linux.intel.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).