[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060830181310.GA11213@powerlinux.fr>
Date: Wed, 30 Aug 2006 20:13:10 +0200
From: Sven Luther <sven.luther@...adoo.fr>
To: David Lang <dlang@...italinsight.com>
Cc: Olaf Hering <olaf@...fle.de>, Michael Buesch <mb@...sch.de>,
Greg KH <greg@...ah.com>, Oleg Verych <olecom@...wer.upol.cz>,
James Bottomley <James.Bottomley@...eleye.com>,
Sven Luther <sven.luther@...adoo.fr>,
debian-kernel@...ts.debian.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MODULE_FIRMWARE for binary firmware(s)
On Wed, Aug 30, 2006 at 10:52:02AM -0700, David Lang wrote:
> On Wed, 30 Aug 2006, Olaf Hering wrote:
>
> >>you are assuming that
> >>
> >>1. modules are enabled and ipw2200 is compiled as a module
> >
> >No, why?
>
> becouse if the ipw isn't compiled as a module then it's initialized
> (without firmware) before the initramfs or initrd is run. if it could be
> initialized later without being a module then it could be initialized as
> part of the normal system
Euh, ...
I wonder why you need to initialize the ipw2200 module so early ? It was my
understanding that the initramfs thingy was run very early in the process, and
i had even thought of moving fbdev modules into it.
Do you really need to bring up ipw2200 so early ? It is some kind of wireless
device, right ?
As for initramfs, you can just cat it behind the kernel, and it should work
just fine, or at least this is how it was supposed to work.
Friendly,
Sven Luther
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists