William, Yes I read all these links, But there are a lot of posts that uEnv.txt way, do have problems, too
BTW, I loaded the my costumed DT (compile my dts to dtbo) within my c program. but I want to the DT auto load, in the 'right way' as it was planned in the first place. regards H. On Monday, December 8, 2014 12:54:26 AM UTC+3, William Hermans wrote: > > http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb > > Seems like you only need to worry about the loading in uEnv.txt. No need > to build from scratch unless you have a custom device tree source file. > > On Sun, Dec 7, 2014 at 2:49 PM, William Hermans <[email protected] > <javascript:>> wrote: > >> Yeah give me a few minutes to see if i can find some information. >> >> On Sun, Dec 7, 2014 at 2:49 PM, hgi <[email protected] <javascript:>> >> wrote: >> >>> Which means that I can not use RCN's trick for loading dt-overlay on >>> boot. >>> >>> but shall I expect to find the base dir for device-tree-overlay ? >>> >>> regards >>> H. >>> >>> On Monday, December 8, 2014 12:44:12 AM UTC+3, William Hermans wrote: >>>> >>>> That is why, There is no capemgr in kernels 3.14.x, 3.15.x, or 3.17 or >>>> above. >>>> >>>> On Sun, Dec 7, 2014 at 2:43 PM, hgi <[email protected]> wrote: >>>> >>>>> the 3.14 kernel : >>>>> root@centralSite1:/home/ubuntu# uname -a >>>>> Linux centralSite1 3.14.22-ti-r31 #1 SMP PREEMPT Sat Oct 25 01:30:27 >>>>> UTC 2014 armv7l armv7l armv7l GNU/Linux >>>>> >>>>> >>>>> >>>>> On Monday, December 8, 2014 12:40:24 AM UTC+3, William Hermans wrote: >>>>>> >>>>>> Ok, so I am not familiar with that image. Which kernel is it using ? >>>>>> >>>>>> On Sun, Dec 7, 2014 at 2:37 PM, hgi <[email protected]> wrote: >>>>>> >>>>>>> @William Hermans >>>>>>> thnx, >>>>>>> but there is no */sys/devices/bo* at all* >>>>>>> >>>>>>> *actually, I'm using BBB Ubuntu 13.04 and 13.10 for a while* >>>>>>> *in both of them, the **/sys/devices/bone_capemgr.8/ and * >>>>>>> */sys/devices/bone_capemgr.9/* >>>>>>> >>>>>>> *dir do exist, respectively * >>>>>>> H. >>>>>>> >>>>>>> On Monday, December 8, 2014 12:30:28 AM UTC+3, William Hermans wrote: >>>>>>>> >>>>>>>> *I have noticed for a missing >>>>>>>>> directory: /sys/devices/bone_capemgr.9/ * >>>>>>>>> >>>>>>>> >>>>>>>> Have you tried >>>>>>>> >>>>>>>> *$ ls -al * >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> */sys/devices/bone_capemgr.*??* >>>>>>>> The path is not guaranteed to be at */sys/devices/bone_* >>>>>>>> *capemgr.9* it could even be at >>>>>>>> */sys/devices/bone_**capemgr.8*. >>>>>>>> >>>>>>>> On Sun, Dec 7, 2014 at 2:21 PM, hgi <[email protected]> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> 1) I DL BBB image from https://rcn-ee.net/deb/flasher/trusty/ >>>>>>>>> Robert-C-Nelson's image the BBB-eMMC-flasher-ubuntu-14.04. >>>>>>>>> 1-console-armhf-2014-10-29-2gb.img.xz >>>>>>>>> and flash it into BBB A6A eMMC, >>>>>>>>> BUT after a short preparations, >>>>>>>>> I have noticed for a missing directory: /sys/devices/bone_c >>>>>>>>> apemgr.9/ >>>>>>>>> >>>>>>>>> it seems a bug, but could I missed something ? >>>>>>>>> someone's assist ? >>>>>>>>> >>>>>>>>> Actually I'm trying to solve the auto load DT on boot, >>>>>>>>> following the notes/answers at my custom capes device tree fails >>>>>>>>> to load at boot but can be loaded manually >>>>>>>>> <http://stackoverflow.com/questions/24134958/my-custom-capes-devicetree-fails-to-load-at-boot-but-can-be-loaded-manually> >>>>>>>>> I planned to use script capemgr-ubuntu.sh I DL from: init_scripts >>>>>>>>> <https://github.com/RobertCNelson/omap-image-builder/tree/master/target/init_scripts> >>>>>>>>> the script read on boot the file (/etc/default/capemgr) content >>>>>>>>> and load the relevant device-tree-overlay >>>>>>>>> >>>>>>>>> >>>>>>>>> 2) >>>>>>>>> where planned Robert-C-Nelson to put capemgr-ubuntu.sh script, in >>>>>>>>> order to be executed on boot ? >>>>>>>>> >>>>>>>>> many thanks in adavance >>>>>>>>> H. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> 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. >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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.
