In message <20001218213325.O1113@dr-evil.shagadelic.org>, Jason R Thorpe writes
:
>...but if you do, make sure to lock the data structure so that another
>process can't come in and frob it underneath you.

In other news, I've established that about half that much delay *does*
seem to be necessary - otherwise, the card Just Doesn't Finish Initializing.

I've also established that the cards work great as long as I have my Mac
running with airport up *FIRST*.  Otherwise, the cards go into a strange
always-busy state.

At which point, I noticed that the BUSY flag is 0x8000, and the WI_EV_TICK
flag is 0x8000, and that no one was handling the TICK interrupts.

So I tried adding WI_EV_TICK to WI_INTRS, and I think it got marginally
better, but not enough better that I can do this without a Mac up and
running yet.  But at least I could ping things for a bit before it started
timing everything out.  :(

Cool!

wi0: oversized packet received (wi_dat_len=10944, wi_status=0x2000)

Note that the most common "busy" status was 0xa000 - sort of like 0x2000 or'd
with 0x8000, as if the card had gotten a clock tick *and* an oversized
packet, or something like that.

Anyway, progress is being made, but I really wish I could figure out why the
card appears to go into a BUSY state all the time if there isn't a Mac handy.

-s