Thanks for the clarification. One suggestion I need. What is the best way to keep up with these changes, because these information is so volatile that it may be redundant in few weeks. Should I go with the source of overlay files and understand from the implementation point of view rather than trying to just make it work somehow. Which source files or functions would be best to start? I just need a direction from where I can start.
On Wednesday, November 8, 2017 at 10:48:54 AM UTC+5:30, RobertCNelson wrote: > > > > On Nov 7, 2017 10:49 PM, "Mrigendra Chaubey" <[email protected] > <javascript:>> wrote: > > That works. > I removed other entried in uEnv.txt and changed it to > enable_uboot_overlays=1 > uboot_overlay_addr0=/lib/firmware/BB-I2C2-ADXL-00A0.dtbo > Now I can see my driver probing. > > One thing happened. I tried to see slots > cat /sys/device/platform/bone.capemgr/slots > cat: slots: No such file or directory > > slots file itself is not present now. > > > Correct, when using U-Boot overlays, the slots file is removed, as it'll > only cause issues. Aka, don't mix and match uboot and kernel overlays. > > Regards, > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8bdcb7bd-c430-4b97-811b-3870856fb9a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
