All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org, linux-modules@vger.kernel.org
Subject: modules: firmware groups attempt two
Date: Tue,  4 Jul 2023 12:50:48 +1000	[thread overview]
Message-ID: <20230704025322.2623556-1-airlied@gmail.com> (raw)

This is a second attempt at firmware grouping so we can have dracut
only pull one firmware into the initramfs instead of a bunch of legacy ones.

v1 got derailed when it was pointed out that ordering isn't consistent in
modinfo with C to sections, so that plan no longer was feasible.

This was the simplest next best option, it keeps the group tags, and
adds a new list of acceptable firmwares. New dracut will ignore legacy
firmware in favour of the list, old dracut will just read the legacy info
lines.

This is ugly because it requires duplication, but I can't think of a nice
way beyond horrible unscaleable C preprocessor tricks to make it nicer.

Dave.



             reply	other threads:[~2023-07-04  2:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  2:50 Dave Airlie [this message]
2023-07-04  2:50 ` [PATCH 1/2] docs: module: start adding some docs for MODULE_ macros Dave Airlie
2023-07-04  2:50   ` Dave Airlie
2023-07-04  2:50 ` [PATCH 2/2] modules/firmware: add a new option to denote a firmware group to choose one Dave Airlie
2023-07-07 18:41   ` Luis Chamberlain
2023-07-07 18:41     ` Luis Chamberlain
2023-07-17 19:41     ` Lucas De Marchi
2023-07-17 19:41       ` Lucas De Marchi
2023-07-18  0:52       ` David Airlie
2023-07-18  0:52         ` David Airlie
2023-07-18 12:28         ` Lucas De Marchi
2023-07-18 12:28           ` Lucas De Marchi

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=20230704025322.2623556-1-airlied@gmail.com \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-modules@vger.kernel.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 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.