This thread has been open for about 8 months. I've got the experience to understand this, and have spent a week looking at it for 3.12.x. There are two things I am certain of:
1) if you want to debug a hotplug event, you have to be logging it in detail. firmware loading requests are hotplug events coming from the kernel. If you are not logging during your debug session, you are guessing. I use busybox's mdev, and recently augmented the load_firmware() infrastructure to do a decent job logging the hotplug events. 2) The first firmware load event coming from 3.12 has the wrong ACTION verb, it has remove rather than add. So tend to indicate a bug in this kernel. Subsequent firmware requests come with the correct action verb, 60 seconds apart. It is possible that if you only have one firmware DTB to load, that your hotplug script is IGNORING the load request because of the bad ACTION verb. Unless you are logging it all, while troubleshooting, you are guessing. In my case there are 3 firmware requests, they all fail. The first fails because of the bad verb, and the 2nd two fail because the firmware files are missing. Without logging I would not have known this. I have two problems to solve now. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
