Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:46621 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752230Ab0CRVUs (ORCPT ); Thu, 18 Mar 2010 17:20:48 -0400 Subject: Re: RFC: A workaround for BCM43XX devices with no on-board SPROM From: Johannes Berg To: Larry Finger Cc: Michael Buesch , bcm43xx devel , wireless In-Reply-To: <4BA296BA.7000502@lwfinger.net> References: <4BA266FB.1080507@lwfinger.net> <1268945580.4005.15.camel@jlt3.sipsolutions.net> <4BA296BA.7000502@lwfinger.net> Content-Type: text/plain; charset="UTF-8" Date: Thu, 18 Mar 2010 14:20:48 -0700 Message-ID: <1268947248.4005.16.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 2010-03-18 at 16:10 -0500, Larry Finger wrote: > On 03/18/2010 03:53 PM, Johannes Berg wrote: > > On Thu, 2010-03-18 at 12:46 -0500, Larry Finger wrote: > >> Michael, > >> > >> I'm switching this discussion from the kernel Bugzilla to the lists. > >> > >> As you know, but I'm restating for anyone that has not read our previous > >> discussions, the b43 driver needs to be changed to handle some of the newer > >> devices do not have an on-board SPROM. It would be trivial to incorporate the > >> data except for the need to have a unique, reproducible MAC. > > > > Where does the data usually come from in these devices? > > It comes from the SPROM, which is missing in the devices in question. Broadcrap > wanted to save a few pennies. Right, but they have to support getting the data somehow on for example windows even if there's no sprom. Do we know where it comes from then? johannes