ROM USB driver order

In the tungsten rom you have

 25 System ROM  USBDriver               0.64    Active
 26 System ROM  EHCIDriver              0.24    Active
 27 System ROM  OHCIDriver              0.40    Active

Would you care to change the order of the OHCIDriver and EHCIDriver so that OHCI is initialised first.

Once they are both installed devices attach to the correct driver when unplugged and plugged in again but during initialisation I have a device which connects to the wrong driver – I don’t think its device related. Changing the order fixes this.

Would you care to change the order of the OHCIDriver and EHCIDriver so that OHCI is initialised first.

Personally, I’d want a little stronger justification than has been given. If subsequent softloading of modules is order independent that’s a bit fishy – are we saying there’s some state in USBDriver which remembers things while the other drivers are killed?

More likely, I suspect, is that the kill/reinit experiment has forgotten that callbacks will trigger while typing the commands whereas they don’t until the end of the ROM init. It’d be better to be robust to either case by changing the code rather than fiddling with ROM orders.

Fairy snuff if I find time to investigate I’ll see what I can do. Its not just a reinit experiment. I’ve reversed the order in the rom I’m running and it works correctly. I thought it may be something to do with callbacks being stacked and not queued this causes OHCI to initialise first. If I ever nail down the problem I’ll come back.