On 6/23/2016 5:22 PM, William Hermans wrote: > Thanks Charles. > > Yes, initially I was thinking that perhaps that file reflected what the > current > values of pins were. But after thinking while waiting for your reply I was > thinking that too. Initial state of the pins at the time the overlay was > loaded. > > Another question regarding config-pin . . .I have a Nodejs project here: > https://github.com/wphermans/Bonejs, but I just now wrote a Nodejs( > Javascript ) > wrapper for config-pin and wanted to make sure that would be ok. I do also > have > plans on using that wrapper for a much bigger, and cooler project, which was > requested by Robert not long ago . . . > > No idea how long it'll take me with other priorities in the mix too. But I > figured I should ask.
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. -- 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/0650e945-ab8c-505a-7b5b-72507a26b14b%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
