public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Faidon Liambotis <paravoid@debian.org>
Cc: David Miller <davem@davemloft.net>,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] firmware: Allow release-specific firmware dir
Date: Thu, 11 Sep 2008 03:15:12 -0400	[thread overview]
Message-ID: <48C8C580.5020803@suse.com> (raw)
In-Reply-To: <48C8BC17.5050508@debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Faidon Liambotis wrote:
> David Miller wrote:
>>> Firmware really _isn't_ version-specific.
>> Tell that to every Debian and Debian derived system on the planet.
>>
>> To my knowledge, it is only fedora and possibly one or two other dists
>> that put the firmware files in a unary /lib/firmware location, rather
>> than a versioned /lib/firmware/$KERNELRELASE one.
> [not speaking on behalf of the project, the kernel team or the
> respective maintainers]
> 
> Apparently and afaik you are misinformed:

Well that's the thing. These are specific firmware packages that exist
outside of those created by the kernel. My original patch wasn't
proposing using /lib/firmware/$KERNELRELEASE for *all* firmware blobs,
just those that are generated and installed by the kernel build process.

The problem occurs when you have multiple versions of the kernel
installed and they all want to put firmware blobs into /lib/firmware.
The firmware blobs created by the kernel aren't versioned liked those in
the examples you've provided, so you end up with a bunch of blobs with
potentially different contents, all with the same names.

I'm not suggesting killing /lib/firmware-located blobs at all. That's
where you look once you discover that /lib/firmware/$KERNELRELEASE
doesn't have the blob you're looking for. That's where firmware packages
like the examples below would still place their files. I see no reason
to change that. If the blobs are versioned so that a particular name
always contains the same contents, that's fine too. What we can't have
is files in the same location with different contents.

In the end, though, Andrew's right. We can't go breaking udev prior to
127 with this.

- -Jeff

> $ dpkg -L firmware-bnx2 (or [1])
> ...
> /lib/firmware/bnx2-06-4.0.5.fw
> /lib/firmware/bnx2-09-4.0.5.fw
> ...
> 
> $ dpkg -L firmware-iwlwifi (or [2])
> ...
> /lib/firmware/iwlwifi-3945-1.ucode
> /lib/firmware/iwlwifi-4965-1.ucode
> /lib/firmware/iwlwifi-4965-2.ucode
> ...
> 
> $ dpkg -L firmware-qlogic (or [3])
> ...
> /lib/firmware/ql2100_fw.bin
> /lib/firmware/ql2200_fw.bin
> /lib/firmware/ql2300_fw.bin
> /lib/firmware/ql2322_fw.bin
> /lib/firmware/ql2400_fw.bin
> /lib/firmware/ql2500_fw.bin
> ...
> 
> etc. for the other firmware packages[4].
> 
> Regards,
> Faidon
> 
> 1: http://packages.debian.org/sid/all/firmware-bnx2/filelist
> 2: http://packages.debian.org/sid/all/firmware-iwlwifi/filelist
> 3: http://packages.debian.org/sid/all/firmware-qlogic/filelist
> 4: http://packages.debian.org/firmware


- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkjIxYAACgkQLPWxlyuTD7LuSgCgmAOte+y8dU1TWODKPNwRnrCK
KO8An1VnOh+KvsfHrgtXZ1H/xSdCYuVL
=3/a7
-----END PGP SIGNATURE-----

  reply	other threads:[~2008-09-11  7:15 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 14:15 [PATCH] firmware: Allow release-specific firmware dir Jeff Mahoney
2008-09-10 22:35 ` Andrew Morton
2008-09-11 13:37   ` Greg KH
2008-09-10 23:01 ` David Woodhouse
2008-09-10 23:05   ` David Miller
2008-09-10 23:15     ` David Woodhouse
2008-09-10 23:24       ` Andrew Morton
2008-09-11  2:55         ` Theodore Tso
2008-09-10 23:24       ` David Miller
2008-09-10 23:36         ` David Woodhouse
2008-09-10 23:42           ` David Miller
2008-09-11  0:23             ` Herbert Xu
2008-09-11  0:39               ` David Woodhouse
2008-09-11  7:44         ` Marcel Holtmann
2008-09-11  8:13           ` Jeff Mahoney
2008-09-11 16:09             ` Marcel Holtmann
2008-09-11  8:29           ` Faidon Liambotis
2008-09-11 16:12             ` Marcel Holtmann
2008-09-11  8:58           ` Frans Pop
2008-09-11 16:16             ` Marcel Holtmann
2008-09-11  8:43       ` Frans Pop
2008-09-11  9:52         ` Frans Pop
2008-09-11 14:50           ` David Woodhouse
2008-09-11 15:24             ` Frans Pop
2008-09-11 15:31               ` David Woodhouse
2008-09-11 15:49                 ` Frans Pop
2008-09-11 15:57                   ` Linus Torvalds
2008-09-11 16:32                     ` Frans Pop
2008-09-11 17:49                       ` Linus Torvalds
2008-09-11 18:24                         ` Frans Pop
2008-09-11 16:01                   ` David Woodhouse
2008-09-11  4:00     ` David Newall
2008-09-11  6:35     ` Faidon Liambotis
2008-09-11  7:15       ` Jeff Mahoney [this message]
2008-09-11 13:38         ` Theodore Tso
2008-09-11 14:36           ` Jeff Mahoney
2008-09-11 16:29             ` Marcel Holtmann
2008-09-11 16:20       ` Marcel Holtmann
2008-09-11 11:29     ` Thierry Vignaud
2008-09-11 13:40       ` Greg KH
2008-09-11 16:39         ` Marcel Holtmann
2008-09-11 16:45           ` David Woodhouse
2008-09-11 20:18             ` Greg KH
2008-09-11 20:15           ` Greg KH
2008-09-11 20:38             ` David Woodhouse
2008-09-11 20:57               ` Greg KH
2008-09-11 21:15                 ` David Woodhouse
2008-09-11 22:07                   ` Greg KH
2008-09-11 22:25                     ` David Woodhouse
2008-09-12  8:39                       ` Joseph Fannin
2008-09-12 13:50                         ` Gene Heskett
2008-09-12 14:32                         ` David Woodhouse
2008-09-12 20:24                           ` Kai Henningsen
  -- strict thread matches above, loose matches on Subject: below --
2011-02-25  2:39 Jeff Mahoney
2011-02-25  5:01 ` Michael Tokarev
2011-02-25 15:03   ` Jeff Mahoney
2011-02-25 16:54     ` David Woodhouse
2011-03-01  0:48 ` Andrew Morton

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=48C8C580.5020803@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paravoid@debian.org \
    --cc=torvalds@linux-foundation.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