Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Johannes Berg
On Thu, 2010-03-18 at 16:20 -0400, John W. Linville wrote: > On Thu, Mar 18, 2010 at 08:31:24PM +0100, Michael Buesch wrote: > > On Thursday 18 March 2010 18:46:35 Larry Finger wrote: > > > > It it reasonable to keep the vendor portion of the MAC and only replace > > > the > > > "serial number",

Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Larry Finger
On 03/18/2010 04:20 PM, Johannes Berg wrote: > 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 list

Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Larry Finger
On 03/18/2010 02:31 PM, Michael Buesch wrote: > On Thursday 18 March 2010 18:46:35 Larry Finger wrote: >> (1) Modify b43-fwcutter to take data from an existing SPROM, > > Why not extend the ssb-sprom tool? I don't think this has anything to do with > firmware, except that we (ab)use the firmware l

Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Larry Finger
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

Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Nicolas de Pesloüan
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

Re: RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Michael Buesch
On Thursday 18 March 2010 18:46:35 Larry Finger wrote: > (1) Modify b43-fwcutter to take data from an existing SPROM, Why not extend the ssb-sprom tool? I don't think this has anything to do with firmware, except that we (ab)use the firmware loading mechanism of the kernel for loading the blob int

RFC: A workaround for BCM43XX devices with no on-board SPROM

2010-03-18 Thread Larry Finger
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 incorpor

Re: No probe response from AP after 500ms, disconnecting.

2010-03-18 Thread Chris Vine
On Wed, 17 Mar 2010 20:09:41 +0100 Miklos Vajna wrote: > Hi, > > I recently upgraded to 2.6.33, then 2.6.34-rc1, but both have the same > bugs: > > 1) The earlier mentioned problem is still there, the b43 driver > disconnects if no WPA is used by the AP. > > (This is not an issue with the binar

Re: No probe response from AP after 500ms, disconnecting.

2010-03-18 Thread Miklos Vajna
On Thu, Mar 18, 2010 at 12:26:32AM +, Chris Vine wrote: > I suggest you add to this thread in linux-acpi (and lkml), that you can > reproduce the problem, and it might then get some attention: > http://marc.info/?l=linux-kernel&m=126879129905898&w=2 . Done. > Out of interest, if you revert