From: "Kevin@Insyde via groups.io" <kevin.davis=insyde.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Renesas uPD720202 USB3 Controller Firmware Binary License
Date: Sun, 6 Oct 2024 16:13:45 +0000 [thread overview]
Message-ID: <7B1B678A-F7FD-4DAD-BFE4-11ADB8D88295@insyde.com> (raw)
In-Reply-To: <c611cf6a-e5d3-4f37-a23b-21d64d465511@bsdio.com>
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
Rebecca,
I’m not an attorney. At Insyde, I have done numerous license reviews. This one would be too restrictive for IBV purposes.
And it restricts it from being used with Open Source Software, which TianoCore would probably be considered, even though TianoCore doesn’t cause any backward licensing.
Of course, an attorney might disagree.
Renesas might be willing to give TianoCore an exception if we explained the situation.
Thanks,
Kevin
_______________________________________________________________
On Oct 5, 2024, at 5:10 PM, Rebecca Cran via groups.io <rebecca=bsdio.com@groups.io> wrote:
I took a look at the firmware loader for the uPD720202 that Ard submitted back in 2017 and after asking Renesas learned that the last version of the firmware is actually publicly available on their site.
It can be downloaded from https://www.renesas.com/en/products/interface/usb-switches-hubs/upd720202-usb-30-host-controller#documents after accepting a license agreement - which I've attached in both the original PDF format and after converting it to plain text.
I'm hoping somebody is better than I am at parsing the legalese and can tell me if we'd be allowed to add the K2026090.mem firmware binary to edk2-non-osi?
There are still a few machines which use it including Ampere Altra based systems, so even after all this time it would be nice if we could add it.
Rebecca
<Disclaimer8.pdf>
<EULA.txt>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120607): https://edk2.groups.io/g/devel/message/120607
Mute This Topic: https://groups.io/mt/108841736/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 3959 bytes --]
prev parent reply other threads:[~2024-10-06 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 21:09 [edk2-devel] Renesas uPD720202 USB3 Controller Firmware Binary License Rebecca Cran
2024-10-06 16:13 ` Kevin@Insyde via groups.io [this message]
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-list 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=7B1B678A-F7FD-4DAD-BFE4-11ADB8D88295@insyde.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox