From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"O'Neal, Terry" <terry.oneal@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package
Date: Fri, 25 Nov 2022 12:02:46 +0100 [thread overview]
Message-ID: <20221125120246.1fed3208@windsurf> (raw)
In-Reply-To: <CH2PR12MB5004D69C65B84BEB0241DB7CF00E9@CH2PR12MB5004.namprd12.prod.outlook.com>
Hello,
On Fri, 25 Nov 2022 09:29:05 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I copied the LICENSE file from the Xilinx/ubuntu-firmware repo below.
> Looking more closely at it, I believe you are right that the license
> should just be Xilinx-Binary-Only.
>
> I will update the LICENSE file to only include the binary portion as
> described in the below license:
> https://github.com/Xilinx/ubuntu-firmware/blob/main/LICENSE
>
> The source code for the versal_plm and versal_psmfw applications
> comes from the same Xilinx/embeddedsw repository as the zynqmp_pmufw,
> so the source and binary licenses for all of these files should be
> the same. https://github.com/Xilinx/embeddedsw/tree/master/lib/sw_apps
Is this the full source code needed to build the versal-firmware? If
so, why do we use a precompiled binary? We should instead build it from
source from this repository.
> If I modify the LICENSE file and remove the commentary about GPL, do
> you think this could be acceptable for inclusion in buildroot? If
> there is anything else I need to add, please let me know.
Yes, if the pre-compiled binaries are distributed under the
Xilinx-Binary-Only license, then that's OK.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-25 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:21 [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package Neal Frager via buildroot
2022-11-24 10:21 ` [Buildroot] [PATCH v6 2/2] configs/versal_vck190: new defconfig Neal Frager via buildroot
2022-11-24 21:15 ` [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package Thomas Petazzoni via buildroot
2022-11-25 9:29 ` Frager, Neal via buildroot
2022-11-25 11:02 ` Thomas Petazzoni via buildroot [this message]
2022-11-25 11:18 ` Frager, Neal via buildroot
2022-11-25 11:33 ` Thomas Petazzoni via buildroot
2022-11-25 13:18 ` Frager, Neal via buildroot
2022-11-25 14:13 ` Thomas Petazzoni via buildroot
2022-11-25 14:14 ` Frager, Neal via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221125120246.1fed3208@windsurf \
--to=buildroot@buildroot.org \
--cc=Kris.Chaplin@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=terry.oneal@amd.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.