Why not disabling the cap manager at the boot (is it possible?) and later push yourself the config that you want in the slot?
Micka, On Dec 10, 2013 5:50 AM, "David Lambert" <[email protected]> wrote: > On 12/09/2013 05:12 PM, Robert Nelson wrote: > >> On Mon, Dec 9, 2013 at 2:15 PM, David Lambert <[email protected]> wrote: >> >>> In desperation, I added a printk to capemgr to print out the return value >>> from request_firmware. I get -2 ENOENT, but the file name is in >>> /lib/firmware exactly as printed in the error line. Another thought is >>> that >>> Debian appears to use initrd, whereas I don't think Angstrom does? Could >>> this be the issue? Any ideas would be very welcome. >>> >> You could try updating the initrd.. >> >> sudo /boot/uboot/tools/update_boot_files.sh >> >> Regards, >> >> Thanks for the suggestion Robert. That is good to know, unfortunately it > did not fix the problem :-( I now suspect that the firmware load request > from capemgr is happening before /lib/firmware is accessible, but this is > just a WAG. I need to understand the way capemgr works before I can offer > any logical explanation :-[ > > Regards, > > Dave. > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
