On Wednesday 18 November 2009 23:07:29 Oncaphillis wrote:
> On 11/18/2009 06:51 PM, Larry Finger wrote:
> > After you get access to the machine, please try my patch. It has been tested
> > here. The first few lines from the output are:
> >
> > ssb: Entering sprom_do_read
> > ssb: Read 0x00002801 from SPROM
> > ssb: Read 0x103C137C from SPROM
> > ssb: Read 0x6DBE0078 from SPROM
> >
> 
> It seems Michaels theory about a missing sprom
> is correct. It gives me:
> 
> [   10.551127] ssb: Found rev 1 PMU (capabilities 0x02A62F01)
> [   10.551143] ssb: Entering sprom_do_read
> [   10.551152] ssb: Read 0xFFFFFFFF from SPROM
> [   10.551159] ssb: Read 0xFFFFFFFF from SPROM

What kind of device is that? Some laptop? I only knew about embedded devices
using these wireless cards without sprom.
Is the card connected via (mini)pci? Or is it on-board?

What we need is a way to identify the card so we avoid accessing
the dangling bus to the sprom. I'd like to avoid the read-the-first-word-
and-check-if-its-all-ones approach, because accesses a dangling bus.
That's obviously no good and can hang the CPU due to missing bus acks.

What's the lspci -vvnn output for the card?

-- 
Greetings, Michael.
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to