BeagleBone Black Networking (wifi and/or wired)

Chris Johns chrisj at rtems.org
Sun Jun 9 02:24:56 UTC 2019


On 8/6/19 1:45 am, Christian Mauderer wrote:
> Note that basically all device tree files that I have found yet are forked from the Linux ones.

Yes, I understand this is the case.

> They are all GPL.

We need to work with these files and respect the license they are under. I think
GPL DTS is OK if these files are not linked into an executable. I am not sure
where you stand in relation to the GPL license if you link a GPL dtb into an
executable. An overlay we create under a suitable license should be fine.

> I think it was Sichen Zhao during 2017 GSoC who wanted to add some to the RTEMS repository and it has been rejected due to the license.

I remember and I still think the position discussed is fine.

> I don't really object to adding them somewhere.

What do we host and maintain? Do we need to host any of these files or should we
have a tool to collect and/or generate the blobs we need.

> But we should think exactly about where we want that stuff.

Having a blob as a file in a system theoretically lets someone update it. The
`dtc` compiler can generate the dts source from a blob so a user can recover the
source, make a change, generate a blob, then return it back into a system if
they wish too.

What about building the FDT blobs we need with the RSB? I know this will work on
FreeBSD and I suspect Linux, MacOS has some issues with clang's cpp.

Chris


More information about the users mailing list