On Fri, Aug 15, 2014 at 9:06 AM, Terje Froysa <[email protected]> wrote: > Thanks for your reply. > > We intend to use this BBB professionally and need to change the pin > configurations at boot.
So the problem is..? > From your reply it seem to me that device overlays cannot be used as > intended. Define "as intended": the overlays work. So unless you like waiting 2 minutes for udev to find the firmware under /lib/firmware/, they are going to be "built-in"... > We can remove and add predefined modules, but not change them... > Is this really true? If "BB-SPIDEV1-00A0.dtbo" is builtin, you can't name something else that and expect your version to be loaded.. The file "build-in" has preference.. > Does that mean that we cannot design a cape with our own ID and > corresponding dtbo? submit a patch like everyone else, and we will roll your "cape" in like everyone else.. https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-BEAGLELOGIC-00A0.dts https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-BONE-REPLICAP-00A1.dts https://github.com/beagleboard/linux/blob/3.8/firmware/capes/cape-bone-argus-00A0.dts > If yes, what will you recommend for us to do to solve the problem? > > If I generate a complete new am335x-boneblack.dtb, will that do? > Or do we have to re-compile the kernel? Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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.
