The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Neal Gompa <neal@gompa.dev>
Cc: Danilo Krummrich <dakr@kernel.org>,
	Russ Weight <russ.weight@linux.dev>,
	Luis Chamberlain <mcgrof@kernel.org>,
	asahi@lists.linux.dev, driver-core@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	Sven Peter <sven@svenpeter.dev>, Janne Grunau <j@jannau.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] firmware_loader: Add /lib/firmware/vendor paths for Apple ARM platforms
Date: Thu, 30 Jul 2026 17:05:13 +0200	[thread overview]
Message-ID: <2026073008-crane-jolly-2204@gregkh> (raw)
In-Reply-To: <CAEg-Je9X8ho7LyiRBL+z9aWf-EdwmgDdrzgfB3KaOaVGiEx_xQ@mail.gmail.com>

On Thu, Jul 30, 2026 at 10:55:00AM -0400, Neal Gompa wrote:
> On Thu, Jul 30, 2026 at 2:01 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Jul 29, 2026 at 08:42:58PM -0400, Neal Gompa wrote:
> > > On Apple ARM machines (branded Apple Silicon Macs), there is
> > > non-redistributable firmware provided in macOS that is required
> > > for Linux to leverage the hardware to run properly.
> > >
> > > The firmware covers Wi-Fi+BT support, USB, hardware ISP, the touchbar
> > > touchscreen, and the trackpad.
> > >
> > > In order to ensure this firmware can be installed without messing
> > > with firmware provided by linux-firmware and other packages that
> > > put things in the tree, the empty "vendor" subdirectory was created
> > > to serve this purpose. This directory is used by the asahi dracut
> > > module as part of the Asahi Linux installation process to transfer
> > > firmware from macOS to the newly installed Linux system.
> >
> > Why is this needed when there is the ability for userspace to add their
> > own firmware search path to the list today?
> >
> > We aren't going to keep adding random paths here, please use the option
> > that is designed specifically for this:
> >
> > >  * fw_path_para - module parameter - default is empty so this is ignored
> >
> > Right there.
> 
> I was not familiar with this feature, and I had inherited the patch as
> part of our cleanup effort to upstream the Asahi work. Sorry about
> that!
> 
> Based on the documentation, this is the patch I've created for our
> dracut module: https://github.com/AsahiLinux/asahi-scripts/pull/72
> 
> Is this how it is supposed to be used?

If it works, yes :)

      reply	other threads:[~2026-07-30 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  0:42 [PATCH] firmware_loader: Add /lib/firmware/vendor paths for Apple ARM platforms Neal Gompa
2026-07-30  6:01 ` Greg Kroah-Hartman
2026-07-30 14:55   ` Neal Gompa
2026-07-30 15:05     ` Greg Kroah-Hartman [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=2026073008-crane-jolly-2204@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=asahi@lists.linux.dev \
    --cc=corbet@lwn.net \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=j@jannau.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=neal@gompa.dev \
    --cc=rafael@kernel.org \
    --cc=russ.weight@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=sven@svenpeter.dev \
    /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