Bill Paul 58a6edd121 When you call MiniportInitialize() for an 802.11 driver, it will ... at some point result in a status event being triggered (it should be a link down event: the Microsoft driver design guide says you should generate one when the NIC is initialized). Some drivers generate the event during MiniportInitialize(), such that by the time MiniportInitialize() completes, the NIC is ready to go. But some drivers, in particular the ones for Atheros wireless NICs, don't generate the event until after a device interrupt occurs at some point after MiniportInitialize() has completed. The gotcha is that you have to wait until the link status event occurs one way or the other before you try to fiddle with any settings (ssid, channel, etc...). For the drivers that set the event sycnhronously this isn't a problem, but for the others we have to pause after calling ndis_init_nic() and wait for the event to arrive before continuing. Failing to wait can cause big trouble: on my SMP system, calling ndis_setstate_80211() after ndis_init_nic() completes, but _before_ the link event arrives, will lock up or reset the system. What we do now is check to see if a link event arrived while ndis_init_nic() was running, and if it didn't we msleep() until it does. Along the way, I discovered a few other problems: - Defered procedure calls run at PASSIVE_LEVEL, not DISPATCH_LEVEL. ntoskrnl_run_dpc() has been fixed accordingly. (I read the documentation wrong.) - Similarly, the NDIS interrupt handler, which is essentially a DPC, also doesn't need to run at DISPATCH_LEVEL. ndis_intrtask() has been fixed accordingly. - MiniportQueryInformation() and MiniportSetInformation() run at DISPATCH_LEVEL, and each request must complete before another can be submitted. ndis_get_info() and ndis_set_info() have been fixed accordingly. - Turned the sleep lock that guards the NDIS thread job list into a spin lock. We never do anything with this lock held except manage the job list (no other locks are held), so it's safe to do this, and it's possible that ndis_sched() and ndis_unsched() can be called from DISPATCH_LEVEL, so using a sleep lock here is semantically incorrect. Also updated subr_witness.c to add the lock to the order list.		2005-03-07 03:05:31 +00:00
..
freebsd32	Use kern_kevent instead of the stackgap for 32bit syscall wrapping.	2005-03-01 17:45:55 +00:00
ia32
linprocfs	Always produce cpuX entries, even in the case when there is only one CPU	2005-03-06 22:28:14 +00:00
linux	Handle unimplemented syscall by instantly returning ENOSYS instead of sending	2005-03-07 00:18:06 +00:00
ndis	When you call MiniportInitialize() for an 802.11 driver, it will	2005-03-07 03:05:31 +00:00
netbsd
pecoff	remove dead code	2005-02-22 01:26:48 +00:00
svr4	fixup signal mapping:	2005-02-25 19:34:10 +00:00