From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] distproto: include the files in /lib/firmware/*
Date: Mon, 8 Mar 2021 12:10:55 +0100 [thread overview]
Message-ID: <CAFSF3XOzHLKwM9gxFM+Snfc8FKfTEus=U+67rfi8KRB9d2+Row@mail.gmail.com> (raw)
In-Reply-To: <MB-zI_cJeOPKs9n9C9FWmjavskhdM41K5USgyENK-XfHeI4_S2AWAs7SDep0ut_lc4PN-TwBeumy20f0PldRZwRzbpcduemUxkuZay8LL_g=@protonmail.com>
the only downside i see is the purity of our distro...
right now it contains just stuff that can be generated from the
source, and maybe some fonts or a few small icons/graphics are the
only binary content
On 3/8/21, kemal <kemali13@protonmail.com> wrote:
>> > I don't think we're going to start redistributing Intel's
>> > firmware, because legal reasons:
>> > https://en.wikipedia.org/wiki/Freely_redistributable_software
>> > (I'm not a lawyer, it'd be nice to be wrong on this)
>>
>> I have checked the firmware license now. Redistribution seems to
>> be permitted without tampering. In addition, patent license
>> actually covers Plan 9. Leaving a copy below.
>
> Would like to add this, Ralink seems to use the same license,
> just all mentions of "Intel Corporation" is replaced with
> "Ralink Technology Corporation".
>
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/LICENCE.ralink-firmware.txt
>
> (i am also not a lawyer of course)
>
>
next prev parent reply other threads:[~2021-03-08 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 17:02 kemal
2021-03-07 17:20 ` ori
2021-03-07 17:36 ` kemal
2021-03-07 18:20 ` ori
2021-03-07 18:58 ` kemal
2021-03-07 19:11 ` kemal
2021-03-08 10:59 ` kemal
2021-03-08 11:10 ` hiro [this message]
2021-03-08 11:58 ` sirjofri
2021-03-08 12:15 ` Sigrid Solveig Haflínudóttir
2021-03-08 12:34 ` Julien Blanchard
2021-03-08 12:44 ` kemal
2021-03-08 12:55 ` hiro
2021-03-08 13:18 ` kemal
2021-03-08 13:28 ` hiro
2021-03-08 13:58 ` kemal
2021-03-08 14:03 ` hiro
2021-03-08 15:32 ` Stanley Lieber
2021-03-08 16:07 ` cinap_lenrek
2021-03-08 17:58 ` kemal
2021-03-08 15:29 ` Stanley Lieber
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='CAFSF3XOzHLKwM9gxFM+Snfc8FKfTEus=U+67rfi8KRB9d2+Row@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).