From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 100461] No BCM43341 uart support on T100TAF
Date: Thu, 25 Jun 2015 10:13:07 +0000 [thread overview]
Message-ID: <bug-100461-62941-VsZxcjeMUu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100461-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=100461
Loic Poulain <loic.poulain@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loic.poulain@intel.com
--- Comment #1 from Loic Poulain <loic.poulain@intel.com> ---
There is some effort to push all broadcom support (config, fw download...) into
the kernel. So This chip should be supported as well.
However for now, you can try the old method consisting in using hciattach to
attach your broadcom device to the kernel. (all the chip config/fw download is
performed in user space).
$ hciattach /dev/ttyS1 bcm43xx
You should see a hci device created.
Be sure that your chip is powered, some broadcom chip gpios are managed by the
rfkill-gpio driver, you may want to unblock the related rfkill node (default
state).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-06-25 10:13 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 ` bugzilla-daemon [this message]
2015-12-17 16:20 ` [Bug 100461] " 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
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-VsZxcjeMUu@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.