From: Jesse Sung <jesse.sung@canonical.com>
To: linux-bluetooth@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>
Subject: [PATCH v2 0/2] Bluetooth: broadcom patchram firmware loader
Date: Tue, 18 Sep 2012 17:49:42 +0800 [thread overview]
Message-ID: <cover.1347959921.git.jesse.sung@canonical.com> (raw)
From: Wen-chien Jesse Sung <jesse.sung@canonical.com>
There is an user space firmware loading tool which can be found at
http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2
This tool requires hci device to do the firmware loading, but this
may cause some race condition between patchram tool and bluetoothd
or something that also works on hci interface.
Also it needs some hooks to make firmware loads after bootup, s3,
s4, rfkill, and device hotplug events. Implement this loader in kernel
module would make things more easier.
Wen-chien Jesse Sung (2):
Introduced a load_firmware callback to struct hci_dev
broadcom patchram firmware loader
drivers/bluetooth/btusb.c | 75 +++++++++++++++++++++++++++++++++++++-
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/hci_core.c | 2 +
3 files changed, 76 insertions(+), 2 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-09-18 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 9:49 Jesse Sung [this message]
2012-09-18 9:49 ` [PATCH v2 1/2] Bluetooth: Introduced a load_firmware callback to struct hci_dev Jesse Sung
2012-09-18 9:49 ` [PATCH v2 2/2] Bluetooth: broadcom patchram firmware loader Jesse Sung
2012-10-04 7:30 ` [PATCH v2 resend 0/2] " Jesse Sung
2012-10-04 7:30 ` [PATCH v2 resend 1/2] Introduced a load_firmware callback to struct hci_dev Jesse Sung
2012-10-04 10:01 ` Marcel Holtmann
2012-10-04 10:37 ` Jesse Sung
2012-10-04 13:06 ` Marcel Holtmann
2012-10-04 13:39 ` Jesse Sung
2012-10-04 18:13 ` Marcel Holtmann
2012-10-04 7:30 ` [PATCH v2 resend 2/2] broadcom patchram firmware loader Jesse Sung
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=cover.1347959921.git.jesse.sung@canonical.com \
--to=jesse.sung@canonical.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).