From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Hector Palacios <hector.palacios@digi.com>,
linux-wireless <linux-wireless@vger.kernel.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>,
mcgrof@do-not-panic.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"surajs@qca.qualcomm.com" <surajs@qca.qualcomm.com>,
jjohnson@qca.qualcomm.com, Adrian Chadd <adrian@freebsd.org>,
ddahlby@qca.qualcomm.com, Ben Hutchings <ben@decadent.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: ROM Patching (was: [PATCH] bluetooth: remove wrong dependency for BT_ATH3K)
Date: Wed, 31 Jul 2013 08:46:22 +0200 [thread overview]
Message-ID: <1375253182.8289.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130730224809.GN17130@pogo> (sfid-20130731_004858_121899_020F19AB)
On Tue, 2013-07-30 at 15:48 -0700, Luis R. Rodriguez wrote:
> Neat. Perhaps we need something that we can share with 802.11 or other
> hardare I highly doubt we're the only ones patching ROM. Don't we even
> patch up core CPUs? I'm wondering if firmware_class could be expanded to
> support serialized ROM patching. The biggest hurdle I see with splititng
> ROM patching from a single firmware is serializing that, addressing
> revision dependencies and of course kernel dependencies.
I don't really see what you're trying to get it so I arbitrarily picked
this ...
I think "ROM patching" like in BT and 802.11 are two completely
different things. In BT at least you have a common transport to the
device, a more-or-less common command set (HCI) etc. None of that exists
for wireless (today) so trying to find common ground between firmware
(patches) for different 802.11 hardware seems completely futile?
johannes
next prev parent reply other threads:[~2013-07-31 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375114325-25498-1-git-send-email-hector.palacios@digi.com>
[not found] ` <5438CD3C-E28C-485C-94B8-F743E8B13D4A@holtmann.org>
[not found] ` <51F7722E.9050708@digi.com>
[not found] ` <20130730205601.GI17130@pogo>
[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 [this message]
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=1375253182.8289.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=ben@decadent.org.uk \
--cc=ddahlby@qca.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=hector.palacios@digi.com \
--cc=jjohnson@qca.qualcomm.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@do-not-panic.com \
--cc=rodrigue@qca.qualcomm.com \
--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 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).