Comment 20 for bug 149997

A valid point. I think a fix that involves only one call to pcmcia_register_driver is the best option. I think the original bug/panic was caused by attempting to register twice when the first call succeeded. My != prevents the second call, but does disable the second set of devices. Is it possible to supply a different struct to MODULE_DEVICE_TABLE and pcmcia_register_driver, but have the table in pcmcia_register_driver be the union of the current orinoco_driver and orinoco_overlap_driver? I'm going to try that here in a minute.