Awesome, that's good to see Linus has accepted the change.

Regarding bonescript, Jason you mentioned:

> With cape-universal, there are gpio and pinmux helpers that can be
configured from userspace.

GPIO and pinmux from userspace sounds great--do you know if there are any
examples of cape-universal and the gpio/pinmux helpers to check out?  If
there was a straightforward way to control GPIO and pinmux from userspace
with those tools then it probably reduces the need for overlays in
libraries like bonescript, BBIO, etc.  Realistically I think BBIO will
probably mirror bonescript's capabilities, so whatever works for bonescript
to dynamically change pins with or without overlays would also work for
BBIO and other libraries.


On Tue, Aug 26, 2014 at 3:01 PM, Robert Nelson <[email protected]>
wrote:

>
>
>
> On Tue, Aug 26, 2014 at 4:50 PM, Jason Kridner <[email protected]>
> wrote:
>
>> On Tue, Aug 26, 2014 at 5:35 PM, William Hermans <[email protected]>
>> wrote:
>>
>>> Jason,
>>>
>>> What is so radically different that capemgr does not work ?
>>>
>>
>> Didn't say that it doesn't work. It hasn't yet been added to our 3.14
>> tree which will require a backport. It looks like it should land upstream
>> in 3.17 and we'll likely backport it from there.
>>
>
> 1 more step:
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ae36e95cf81c98b111b84317adeb358aaffa80e2
>
> Group changes to the device tree. In preparation for adding device tree
> overlay support, OF_DYNAMIC is reworked so that a set of device tree
> changes can be prepared and applied to the tree all at once. OF_RECONFIG
> notifiers see the most significant change here so that users always get a
> consistent view of the tree. Notifiers generation is moved from before a
> change to after it, and notifiers for a group of changes are emitted after
> the entire block of changes have been applied
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/ULhioCVzbYk/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Reply via email to