Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755270Ab3GaHsw (ORCPT ); Wed, 31 Jul 2013 03:48:52 -0400 Received: from mail-la0-f54.google.com ([209.85.215.54]:39903 "EHLO mail-la0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754260Ab3GaHsu (ORCPT ); Wed, 31 Jul 2013 03:48:50 -0400 MIME-Version: 1.0 In-Reply-To: <1375253182.8289.3.camel@jlt4.sipsolutions.net> References: <1375114325-25498-1-git-send-email-hector.palacios@digi.com> <5438CD3C-E28C-485C-94B8-F743E8B13D4A@holtmann.org> <51F7722E.9050708@digi.com> <20130730205601.GI17130@pogo> <2C94C740-76BA-4058-B0D7-C37D44875CA1@holtmann.org> <20130730224809.GN17130@pogo> <1375253182.8289.3.camel@jlt4.sipsolutions.net> From: "Luis R. Rodriguez" Date: Wed, 31 Jul 2013 00:48:28 -0700 X-Google-Sender-Auth: fnBo443c5Uv2vIuHSKLkbxJDQMk Message-ID: Subject: Re: ROM Patching (was: [PATCH] bluetooth: remove wrong dependency for BT_ATH3K) To: Johannes Berg Cc: Marcel Holtmann , Hector Palacios , linux-wireless , "linux-bluetooth@vger.kernel.org" , "gustavo@padovan.org" , "johan.hedberg@gmail.com" , "linux-kernel@vger.kernel.org" , "surajs@qca.qualcomm.com" , jjohnson@qca.qualcomm.com, Adrian Chadd , ddahlby@qca.qualcomm.com, Ben Hutchings , Greg Kroah-Hartman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1390 Lines: 33 On Tue, Jul 30, 2013 at 11:46 PM, Johannes Berg 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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/