usbhandler.sh needs to support multiple modules per device
|Status:||In Progress||Start date:||07 May 2014|
|Category:||04 - Root File System|
|Target version:||3.0 - Corrino|
|Severity:||03 - Medium|
Its possible that a device might need multiple modules loaded, and in a given order. Currently usbhandler doesn't support this.
#1 Updated by Hammel about 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
- S10usbdev which does sort of what usbhandler.sh was doing, but badly.
- mdev.conf, which probably loads the WinTV drivers via MODALIAS or one of the v4l entries.
- A usbhandler.sh which does mostly what it should if it were passed the correct data.
- Fix usbhandler.sh to operate via init script or mdev. This means using functions and testing input args to determine who is calling the script.
- Change S10usbdev to call usbhandler.sh
- Move S10usbdev ahead of S10mdev
- Change mdev.conf to call usbhandler.sh for usb devices first - before any other handler is called for the device, ignoring those it can't handle.
After fixing all this I can then add multiple lines for the WinTV device to usbhandler.conf to allow loading multiple drivers in the correct order.
The key to all this is to make sure the init scripts don't load the WinTV drivers before I get a chance to load them in the correct order first.
#2 Updated by Hammel about 6 years ago
- Priority changed from Immediate to Low
- Target version changed from 0.9.0 to 3.0 - Corrino
- Severity changed from 01 - Critical to 03 - Medium
Turns out that the drivers are getting loaded no matter what and the drivers work with w_scan IF the Pi has its own power supply separate from the external hub (the Pi is not powered through the powered hub). So none of this is need as of now. It may be useful later, though.
I'll drop this to very low priority and target for a much later release.