From: Andi Kleen <andi@firstfloor.org>
To: Olivier Galibert <galibert@pobox.com>,
Takashi Iwai <tiwai@suse.de>,
David Woodhouse <dwmw2@infradead.org>,
Hannes Reinecke <hare@suse.de>, Theodore Tso <tytso@mit.edu>,
Jeff Garzik
Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"
Date: Sat, 05 Jul 2008 13:22:20 +0200 [thread overview]
Message-ID: <486F596C.8050109@firstfloor.org> (raw)
In-Reply-To: <20080705105317.GA44773@dspnet.fr.eu.org>
Olivier Galibert wrote:
> On Sat, Jul 05, 2008 at 09:41:56AM +0200, Takashi Iwai wrote:
>> Yes, it will, if the firmware blobs are packed into the kernel
>> package. In a long term, we can put firmware files into a separate,
>> architecture independent noarch package, though. This will save the
>> total package size, too.
>
> That could be interestingly hard, actually. Right now the kernel
> package is one of these packages designed so that multiple versions
> can be installed together. When the version of one of the firmwares
> changes, the firmware package will have to be updated. But will it
> keep the previous version? If it doesn't, the possibly still
> installed older kernels won't work anymore. If it does, it will
> accumulate a lot of files over time...
Many distribution have some way for separate kernel module packages.
It's essentially the same problem so it should be already solved
in some way. Also there are already drivers who rely on separate
firmware so they already should have this problem (and hopefully
a solution). Of course these existing solutions might not be good
enough. And a lot of people ignored them because they didn't use
these external packages and drivers with those requirements.
I agree with you that doing this for more drivers will be a further complication
and the rationale why this complication is needed for drivers like tg3 or
e100 so far didn't sound very convincing to me. If I read it correctly it
was "some other drivers do it this way so let's complicate everybody and
put them on the same level". Perhaps I'm dense, but I failed
to see the convincing reason in that.
On the other hand for my personal use it this change should be
transparent, at least as long as "make firmware_install"
will be integrated into "make modules_install" and put the files somewhere where
they don't conflict with other versions.
-Andi
next prev parent reply other threads:[~2008-07-05 11:22 UTC|newest]
Thread overview: 142+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080703020236.adaa51fa.akpm@linux-foundation.org>
2008-07-03 11:59 ` [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" KOSAKI Motohiro
2008-07-03 12:21 ` Jeff Garzik
2008-07-03 13:04 ` Hugh Dickins
2008-07-03 13:11 ` Jeff Garzik
2008-07-03 13:33 ` David Woodhouse
2008-07-03 13:38 ` Jeff Garzik
2008-07-03 13:52 ` David Woodhouse
2008-07-03 17:30 ` Theodore Tso
2008-07-03 18:56 ` David Woodhouse
2008-07-03 19:31 ` Valdis.Kletnieks
2008-07-03 19:49 ` David Woodhouse
2008-07-03 20:52 ` Rafael J. Wysocki
2008-07-03 21:03 ` Jeff Garzik
2008-07-03 21:33 ` David Woodhouse
2008-07-03 21:42 ` Rafael J. Wysocki
2008-07-03 21:43 ` David Woodhouse
2008-07-03 21:52 ` Rafael J. Wysocki
2008-07-03 21:54 ` David Woodhouse
2008-07-03 22:27 ` Rafael J. Wysocki
2008-07-03 22:22 ` Jeff Garzik
2008-07-03 22:25 ` Alan Cox
2008-07-03 23:14 ` Jeff Garzik
2008-07-03 23:02 ` Alan Cox
2008-07-04 2:31 ` Mikael Pettersson
2008-07-03 23:21 ` David Miller
2008-07-04 0:18 ` Theodore Tso
2008-07-04 1:09 ` David Woodhouse
2008-07-04 1:47 ` Theodore Tso
2008-07-04 0:24 ` David Woodhouse
2008-07-04 1:28 ` Grant Coady
2008-07-04 2:42 ` david
2008-07-04 10:07 ` David Woodhouse
2008-07-04 10:09 ` Andi Kleen
2008-07-04 13:10 ` David Woodhouse
2008-07-04 13:15 ` Jeff Garzik
2008-07-04 13:27 ` David Woodhouse
2008-07-04 13:39 ` Jeff Garzik
2008-07-04 13:27 ` Alan Cox
2008-07-04 13:48 ` David Woodhouse
2008-07-04 14:06 ` Jeff Garzik
2008-07-04 20:43 ` David Miller
2008-07-04 21:04 ` Alan Cox
2008-07-06 20:17 ` david
2008-07-06 20:27 ` David Woodhouse
2008-07-06 20:51 ` Jeff Garzik
2008-07-06 20:52 ` david
2008-07-06 20:56 ` David Woodhouse
2008-07-06 21:03 ` david
2008-07-06 21:38 ` Jeff Garzik
2008-07-06 22:10 ` David Woodhouse
2008-07-06 23:22 ` Jeff Garzik
2008-07-05 6:05 ` Jeff Garzik
2008-07-07 17:52 ` Rick Jones
2008-07-04 13:46 ` David Woodhouse
2008-07-04 14:07 ` Jeff Garzik
2008-07-04 14:38 ` Alan Cox
2008-07-06 23:40 ` Jeff Garzik
2008-07-07 15:53 ` Alan Cox
2008-07-07 17:24 ` Jeff Garzik
2008-07-07 18:13 ` Alan Cox
2008-07-07 18:57 ` Jeff Garzik
2008-07-07 18:30 ` Alan Cox
2008-07-07 19:16 ` Jeff Garzik
2008-07-07 18:45 ` Alan Cox
2008-07-07 19:48 ` Jeff Garzik
2008-07-07 20:48 ` David Miller
2008-07-07 20:42 ` Alan Cox
2008-07-07 21:45 ` David Miller
2008-07-07 21:14 ` Alan Cox
2008-07-07 21:58 ` David Miller
2008-07-08 6:36 ` Alan Cox
2008-07-08 8:57 ` David Miller
2008-07-04 14:30 ` Theodore Tso
2008-07-04 14:37 ` David Woodhouse
2008-07-04 18:01 ` David Woodhouse
2008-07-04 20:28 ` Sam Ravnborg
2008-07-05 4:35 ` Jeff Garzik
2008-07-04 20:39 ` David Miller
2008-07-04 14:10 ` Theodore Tso
2008-07-04 14:23 ` Takashi Iwai
2008-07-04 14:39 ` Hannes Reinecke
2008-07-04 14:42 ` David Woodhouse
2008-07-04 21:34 ` Grant Coady
2008-07-04 22:08 ` David Woodhouse
2008-07-04 23:13 ` Olivier Galibert
2008-07-04 23:58 ` Henrique de Moraes Holschuh
[not found] ` <20080704235839.GA5649@khazad-dum.debian.net>
2008-07-05 0:51 ` Trent Piepho
2008-07-05 3:52 ` Henrique de Moraes Holschuh
2008-07-05 6:01 ` Bill Fink
2008-07-05 13:08 ` Henrique de Moraes Holschuh
2008-07-05 4:10 ` Jeff Garzik
2008-07-05 7:41 ` Takashi Iwai
2008-07-05 8:50 ` David Woodhouse
2008-07-05 10:53 ` Olivier Galibert
2008-07-05 11:22 ` Andi Kleen [this message]
2008-07-05 12:02 ` Olivier Galibert
2008-07-05 12:09 ` Andi Kleen
2008-07-05 12:16 ` David Woodhouse
2008-07-05 12:23 ` Andi Kleen
2008-07-05 12:42 ` David Woodhouse
2008-07-05 13:57 ` Andi Kleen
2008-07-05 14:44 ` Olivier Galibert
2008-07-05 15:10 ` David Woodhouse
2008-07-05 17:13 ` Christoph Hellwig
2008-07-05 20:55 ` David Woodhouse
2008-07-06 10:02 ` Christoph Hellwig
2008-07-06 10:55 ` David Woodhouse
2008-07-06 11:50 ` Andi Kleen
2008-07-06 12:22 ` David Woodhouse
2008-07-04 14:44 ` Takashi Iwai
2008-07-04 14:24 ` maximilian attems
2008-07-04 14:36 ` Theodore Tso
2008-07-05 10:26 ` maximilian attems
2008-07-04 14:31 ` David Woodhouse
2008-07-04 20:37 ` David Miller
2008-07-04 20:42 ` Arjan van de Ven
2008-07-04 20:43 ` David Woodhouse
2008-07-04 20:52 ` David Miller
2008-07-04 21:05 ` David Woodhouse
2008-07-05 4:05 ` Valdis.Kletnieks
2008-07-04 20:51 ` David Miller
2008-07-04 20:59 ` Arjan van de Ven
2008-07-04 21:12 ` David Woodhouse
2008-07-04 21:10 ` Alan Cox
2008-07-04 20:53 ` David Woodhouse
2008-07-05 4:04 ` Jeff Garzik
2008-07-04 13:42 ` Andi Kleen
2008-07-03 20:34 ` David Miller
2008-07-03 20:54 ` David Woodhouse
2008-07-09 20:43 ` Alexandre Oliva
2008-07-04 11:06 ` Takashi Iwai
2008-07-04 13:17 ` David Woodhouse
2008-07-04 13:26 ` Takashi Iwai
2008-07-04 13:28 ` David Woodhouse
2008-07-04 13:42 ` Jeff Garzik
2008-07-04 13:45 ` David Woodhouse
2008-07-04 14:10 ` Jeff Garzik
2008-07-04 14:13 ` David Woodhouse
2008-07-05 6:14 ` Jeff Garzik
2008-07-04 13:28 ` Jeff Garzik
2008-07-03 16:10 ` Chuck Lever
2008-07-05 5:49 Jaswinder Singh
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=486F596C.8050109@firstfloor.org \
--to=andi@firstfloor.org \
--cc=dwmw2@infradead.org \
--cc=galibert@pobox.com \
--cc=hare@suse.de \
--cc=tiwai@suse.de \
--cc=tytso@mit.edu \
/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).