BeagleBone Black Networking (wifi and/or wired)

[Gedare Bloom]

On Sat, Jun 8, 2019 at 8:25 PM Chris Johns <chrisj at rtems.org> wrote:
>
> 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.
>

If you apply the overlay using host tools, then the license
implications are problematic since you will be distributing a binary
program that is combining GPL code, the entire image comes under GPL.
Building the overlay online is more defensible, since you can
distribute the dtb separately.

> > 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
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users