On Fri, 2006-04-14 at 10:35 +1000, Benjamin Herrenschmidt wrote: > On Fri, 2006-04-14 at 10:02 +1000, Benjamin Herrenschmidt wrote: > > I get that with current upstream git : > > .../... > > Correction: It actually works after tickling softmac a bit (it's an open > network with non advertised essid, the init scripts are supposedly > setting the essid but softmac is having some vapors, changing the essid > manually a couple of times and it ends up associating). Below ... > Still, the dmesg filling up with those messages is pretty nasty :) There are two issues here. One is the messages (related to it being a 0x4318) and secondly that softmac isn't behaving will :) I'm trying to fix the latter but can't really pinpoint the problem yet. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Current linus git bcm4xxx broken for me
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Current linus git bcm4xxx broken for me
- From: Benjamin Herrenschmidt <[email protected]>
- Current linus git bcm4xxx broken for me
- Prev by Date: A puzzle: CAPZLOQ TEKNIQ 1.0
- Next by Date: Re: [Devel] Re: [RFC] Virtualization steps
- Previous by thread: Re: Current linus git bcm4xxx broken for me
- Next by thread: Re: Current linus git bcm4xxx broken for me
- Index(es):