Hi Alan,
Thanks for all the suggestions!
On 10/16/18 13:04, Alan Tull wrote:
> On Mon, Oct 15, 2018 at 7:28 PM wrote:
>
> Hi Frank,
>
> Thanks for all your work on this!
>
>> From: Frank Rowand
>>
>> When an overlay is applied or removed, the live devicetree visible in
>> /proc/device-tree/
On Mon, Oct 15, 2018 at 7:28 PM wrote:
Hi Frank,
Thanks for all your work on this!
> From: Frank Rowand
>
> When an overlay is applied or removed, the live devicetree visible in
> /proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
> changes. There is no method for user space
On 10/15/18 17:35, valdis.kletni...@vt.edu wrote:
> On Mon, 15 Oct 2018 17:27:01 -0700, frowand.l...@gmail.com said:
>> From: Frank Rowand
>>
>> When an overlay is applied or removed, the live devicetree visible in
>> /proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
>> changes.
On Mon, 15 Oct 2018 17:27:01 -0700, frowand.l...@gmail.com said:
> From: Frank Rowand
>
> When an overlay is applied or removed, the live devicetree visible in
> /proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
> changes. There is no method for user space to determine whether
From: Frank Rowand
When an overlay is applied or removed, the live devicetree visible in
/proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
changes. There is no method for user space to determine whether the
live devicetree was modified by overlay actions.
Provide a sysfs file
5 matches
Mail list logo