9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] distproto: include the files in /lib/firmware/*
Date: Mon, 08 Mar 2021 10:29:15 -0500	[thread overview]
Message-ID: <56C2E381-779A-4FE9-AD52-C1994C386A06@stanleylieber.com> (raw)
In-Reply-To: <6cbbf99c-e422-4183-8954-a794a042d690@sirjofri.de>

On March 8, 2021 6:58:49 AM EST, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>08.03.2021 12:10:55 hiro <23hiro@gmail.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
>
>I think it is very convenient to have some firmware in the released iso 
>images. I wouldn't add them to the repo, adding links to them like the 
>fqa already does is good enough, I think. Since we have the /lib/firmware 
>directory and it's basically enough to place the files there I don't 
>think too many adjustments are needed, adding mkfile rules for 
>downloading the firmware files and packing an iso would be convenient for 
>automatic packing (I am thinking about doing daily iso images on a server 
>as well as providing a mirror for 9front isos. Imagine a rule for the 
>bare iso without firmware and another rule for release isos with 
>firmware).
>
>(I am not a lawyer.)
>
>Just my two cents.
>
>sirjofri
>

how do we decide which firmware to include and which firmware to ignore?

sl

      parent reply	other threads:[~2021-03-08 15:34 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
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 [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-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=56C2E381-779A-4FE9-AD52-C1994C386A06@stanleylieber.com \
    --to=sl@stanleylieber.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).