Hi,
I have been tinkering around with the iDroid project (making Android run on iPod Touches and iPhones). However, I believe that my question is more encompassing than just for that project.
There are several devices on the iPod which require firmware to be loaded to them. The device drivers request their firmware approximately 5 seconds into the boot process, which is well before I can actually run programs. Init takes over at ~20 seconds, and mdev is set up and run at ~23. For some reason, mdev doesn't seem to detect that the devices have requested firmware, and the firmware cannot load until the request times out (I believe 60 seconds) and retries. This means that the device takes some 30 seconds longer than necessary to actually load firmware.
My question: is it possible to force a firmware request to time out? If not, is it possible to make it so that mdev can correctly detect firmware requests that were made before /proc/sys/kernel/hotplug is set to /sbin/mdev?
Thank you,
Connor
I have been tinkering around with the iDroid project (making Android run on iPod Touches and iPhones). However, I believe that my question is more encompassing than just for that project.
There are several devices on the iPod which require firmware to be loaded to them. The device drivers request their firmware approximately 5 seconds into the boot process, which is well before I can actually run programs. Init takes over at ~20 seconds, and mdev is set up and run at ~23. For some reason, mdev doesn't seem to detect that the devices have requested firmware, and the firmware cannot load until the request times out (I believe 60 seconds) and retries. This means that the device takes some 30 seconds longer than necessary to actually load firmware.
My question: is it possible to force a firmware request to time out? If not, is it possible to make it so that mdev can correctly detect firmware requests that were made before /proc/sys/kernel/hotplug is set to /sbin/mdev?
Thank you,
Connor