All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 100461] No BCM43341 uart support on T100TAF
Date: Sat, 09 Jan 2016 10:45:29 +0000	[thread overview]
Message-ID: <bug-100461-62941-hdytYhY1lt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100461-62941@https.bugzilla.kernel.org/>

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

--- Comment #8 from Weiwu Zhang <zhangweiwu@realss.com> ---
(In reply to jbMacAZ from comment #7)
> I had the same result. The solution is to move the BCM4324B.hcd file up 1
> folder from /lib/firmware/brcm/ to /lib/firmware/  I don't understand why
> that would matter, so YMMV.

It's amazing! Yes, you are right! In my case, simply moving it to /lib/firmware
made the last 3 bytes of BD address change from 00-00-00 to 00:1F:AC.

It's so unreasonable!

> The btattach still won't return, but the BD Address from hciconfig is real
> and it is possible to pair bt devices. 

In my case btattach runs (although it doesn't fork to background like the
tutorial suggested). If I enable bluetooth ($ sudo hciconfig hci1 up) I can
scan devices.

To connect and pair devices, the bluetooth shipped with Ubuntu 15.10 won't
work. blueman (launch with blueman-manager)'s "add new device" wizard works for
me.

It's the first time I got bluetooth mouse working since I bought the computer
one year ago.

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

      parent reply	other threads:[~2016-01-09 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  9:48 [Bug 100461] New: No BCM43341 uart support on T100TAF bugzilla-daemon
2015-06-25 10:13 ` [Bug 100461] " bugzilla-daemon
2015-12-17 16:20 ` bugzilla-daemon
2015-12-18  8:19 ` bugzilla-daemon
2015-12-23 12:48 ` bugzilla-daemon
2015-12-29 16:04 ` bugzilla-daemon
2016-01-06  6:53 ` bugzilla-daemon
2016-01-06 19:54 ` bugzilla-daemon
2016-01-09 10:45 ` bugzilla-daemon [this message]

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=bug-100461-62941-hdytYhY1lt@https.bugzilla.kernel.org/ \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.