From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Hector Palacios <hector.palacios@digi.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"gustavo@padovan.org" <gustavo@padovan.org>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"surajs@qca.qualcomm.com" <surajs@qca.qualcomm.com>
Subject: Re: [PATCH] bluetooth: remove wrong dependency for BT_ATH3K
Date: Tue, 30 Jul 2013 13:56:01 -0700 [thread overview]
Message-ID: <20130730205601.GI17130@pogo> (raw)
In-Reply-To: <51F7722E.9050708@digi.com>
On Tue, Jul 30, 2013 at 09:58:38AM +0200, Hector Palacios wrote:
> This brings an interesting question: shouldn't the firmware download
> part be isolated from the USB driver? After all, I want to
> communicate with a UART bluetooth chip.
There are a few BT firmware upload modules (last I checked at least 2),
I believe it should be possible to stuff all that code a shared
module or even as FreeBSD does it -- treat fw uploading in userspace,
however just keep in mind for quirks [0]. So patches welcomed.
[0] http://wireless.kernel.org/en/users/Drivers/ath3k#AR3011_over_USB
Luis
next prev parent reply other threads:[~2013-07-30 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 16:12 [PATCH] bluetooth: remove wrong dependency for BT_ATH3K Hector Palacios
2013-07-29 16:43 ` Marcel Holtmann
2013-07-30 7:58 ` Hector Palacios
2013-07-30 20:56 ` Luis R. Rodriguez [this message]
[not found] ` <2C94C740-76BA-4058-B0D7-C37D44875CA1@holtmann.org>
2013-07-30 22:48 ` ROM Patching (was: [PATCH] bluetooth: remove wrong dependency for BT_ATH3K) Luis R. Rodriguez
2013-07-30 23:55 ` Greg Kroah-Hartman
2013-07-31 0:27 ` Luis R. Rodriguez
2013-07-31 6:46 ` Johannes Berg
2013-07-31 7:48 ` Luis R. Rodriguez
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=20130730205601.GI17130@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=gustavo@padovan.org \
--cc=hector.palacios@digi.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=surajs@qca.qualcomm.com \
/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.