Comment 17 for bug 149997

My understanding is that the orinoco_driver set of PCMCIA IDs is exported to allow auto-detection of those devices as belonging to orinoco_cs. IOW, if a device with an ID in orinoco_driver is hotplugged, orinoco_cs will automatically be loaded to support this device. Devices in orinoco_overlap_driver are also (theoretically) supported by hostap, and thus not advertised as orinoco_cs supported. So for those devices, a manual modprobe must be done. For those devices, the first call to pcmcia_register_driver will fail, and then the driver retries with orinoco_overlap_driver. Are there any known instances where the change from >= to != would cause a failure? I'm rebuilding a kernel package now to test on a couple of systems with orinoco wireless cards. I don't have any hostap+orinoco cards to test with.