On Tue, Jul 30, 2013 at 11:46 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > 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. Sure. > None of that exists > for wireless (today) so trying to find common ground between firmware > (patches) for different 802.11 hardware seems completely futile? So long as we can gaurantee mobile drivers get fw updated as much as is really needed in the industry great. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
