Just as an indication of what I'm looking at. debian@beaglebone:~$ ls /lib/firmware/ |grep univ cape-univ-audio-00A0.dtbo cape-univ-emmc-00A0.dtbo cape-univ-hdmi-00A0.dtbo cape-universal-00A0.dtbo cape-universaln-00A0.dtbo univ-all-00A0.dtbo univ-bbgw-00A0.dtbo univ-emmc-00A0.dtbo univ-hdmi-00A0.dtbo univ-nhdmi-00A0.dtbo
My guess is that I want the last one, but without checking the source ( which I can do on github now that I think on it ), how could I know ? Ill check on github for now . . . On Fri, Jun 24, 2016 at 10:22 AM, William Hermans <[email protected]> wrote: > Charles, > > So one thing I do find kind of confusing. Is which universal-io device > tree to load at boot. Basicaly, my board is currently set stock + hdmi > audio, and video disabled. > > Could you please give me a rundown on what each dtb is for ? I'll document > that information and write up a blog post on it for future reference. > > Additionally, while I'm here posting questions. What would be the best way > to have pins enabled in a specific way at boot ? Just modify the dtbs file > to reflect my preferences, and recompile ? > > On Thu, Jun 23, 2016 at 5:52 PM, William Hermans <[email protected]> > wrote: > >> Okay . . . >> >> Went through the file and replaced sudo -A for '' ( empty string- or null >> ). And then had to add to my udev rules file . . . >> >> SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio >> /sys/class/gpio; chmod -R 770 /sys/class/gpio; chown -R root:gpio >> /sys/devices/platform/ocp/4????000.gpio/gpio/; chmod -R 770 >> /sys/devices/platform/ocp/4????000.gpio/gpio/; chown root:gpio >> /sys/devices/platform/ocp/ocp:??_??_pinmux/state; chmod 770 >> /sys/devices/platform/ocp/ocp:??_??_pinmux/state'" >> >> On Thu, Jun 23, 2016 at 5:28 PM, William Hermans <[email protected]> >> wrote: >> >>> Ok so one not so fun issue . . . >>> >>> william@beaglebone:~/dev/bonejs$ config-pin P8.07 low >>> sudo: no askpass program specified, try setting SUDO_ASKPASS >>> Cannot write gpio direction file: /sys/class/gpio/gpio66/direction >>> >>> EXCEPT >>> william@beaglebone:~/dev/bonejs$ ls -al /sys/class/gpio/gpio66/direction >>> -rwxrwx--- 1 root *gpio* 4096 Jun 23 14:17 >>> /sys/class/gpio/gpio66/direction >>> >>> william@beaglebone:~/dev/bonejs$ getent group gpio >>> *gpio*:x:1001:william >>> >>> I've a feeling I know how to fix this though . . . will require editing >>> config-pin . . . >>> >>> >>> >>> >>> On Thu, Jun 23, 2016 at 3:57 PM, William Hermans <[email protected]> >>> wrote: >>> >>>> Wrap away! >>>>> >>>>> I'm just happy the universal overlay concept has caught-on. I wanted >>>>> people to be able to do most simple things without having to craft >>>>> custom device-tree overlays. Using a custom overlay is still the most >>>>> flexible option, but there's a pretty high barrier to entry. >>>>> >>>> >>>> Ok awesome. >>>> >>>> I've actually really liked the idea of universal-io ever since you put >>>> the project up, and made it known. Really an awesome idea. At the time it >>>> was very obvious to me that this would be something really cool. But I was >>>> wrapped up in my own little world, doing my own thing, and since I use >>>> console images that do not always, or ever seem to have config-pin enabled >>>> by default ? Not really sure, but every time I went to tinker with >>>> config-pin . . . "command not found". It's just that this time, my own >>>> little world collided with universal-io. So I gave some thought into what >>>> actually was not working, and how to make it work. >>>> >>>> I do have to say, that I'm every bit as impressed with universal-io >>>> now, as I was back when you put it into the wild. I quite honestly think >>>> that universal-io + config-pin is every bit as good as device tree files. >>>> At least in what universal-io can do. I do not know if it has any short >>>> comings. but from what I can see . . . there are none ? >>>> >>>> >>>> On Thu, Jun 23, 2016 at 3:41 PM, Charles Steinkuehler < >>>> [email protected]> wrote: >>>> >>>>> On 6/23/2016 5:26 PM, William Hermans wrote: >>>>> > >>>>> > So the wrapper is really simple. But what I plan on doing with said >>>>> wrapper will >>>>> > be really neat I think. How does configurering your pin modes from a >>>>> web page >>>>> > sound ? ;) >>>>> >>>>> That sounds pretty awesome! >>>>> >>>>> -- >>>>> Charles Steinkuehler >>>>> [email protected] >>>>> >>>>> -- >>>>> 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/b8bacad4-1c9c-46fe-1cdf-243632cb85cd%40steinkuehler.net >>>>> . >>>>> 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrkPCUhyd31%2BNquK89%3DVb%3DWxFG1L6EODf_%2B9_BHpzgYyA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
