On Thu, Oct 5, 2017 at 1:34 PM, Mrigendra Chaubey <[email protected]> wrote: >> One small question that is not related to upper discussion. > > On beaglebone, i2c-2 instance,that is on pins p9_19 and p9_20. Is this > mapped as i2c1?
i2c-2/i2c-1 is a bug in 3.8.13 > If this is already mapped, why do I(or people) need to create an overlay > file?Its already there. Usually we just define the hardware at the i2c location.. > Also if I do create an overlay file and compile it and put it into > /lib/firmware, and invoke slot mechanism of bonmgr, it gets a slot. But it > is not discover able on reboot again. Is it? Not unless you tell it to load it.. > So how do I add an i2c device permanently whenever my bbb boots up? There's a few ways, since your using 3.8.13, stick the name in: /etc/default/capemgr or write an init scrip to do it.. > How is > device tree better than previous board file concept? if you just "booted" supported devices no difference. If your working on new designs, modifcations, etc... it's a whole lot easer.. Regards, -- Robert Nelson https://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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhTfnZvm4RkuuEeezN-b5OCxX_7-UXJ_rtj8rj_gzb9vw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
