public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: David Lang <dlang@digitalinsight.com>
Cc: Olaf Hering <olaf@aepfle.de>, Michael Buesch <mb@bu3sch.de>,
	Greg KH <greg@kroah.com>, Oleg Verych <olecom@flower.upol.cz>,
	James Bottomley <James.Bottomley@steeleye.com>,
	Sven Luther <sven.luther@wanadoo.fr>,
	debian-kernel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MODULE_FIRMWARE for binary firmware(s)
Date: Wed, 30 Aug 2006 20:13:10 +0200	[thread overview]
Message-ID: <20060830181310.GA11213@powerlinux.fr> (raw)
In-Reply-To: <Pine.LNX.4.63.0608301048180.31356@qynat.qvtvafvgr.pbz>

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

  reply	other threads:[~2006-08-30 18:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 22:08 [PATCH] MODULE_FIRMWARE for binary firmware(s) James Bottomley
2006-08-28 22:11 ` James Bottomley
2006-08-28 23:04   ` Sven Luther
2006-08-28 23:50     ` James Bottomley
2006-08-29  0:35     ` Oleg Verych
2006-08-28 23:55       ` James Bottomley
2006-08-29  2:15         ` Oleg Verych
     [not found]           ` <20060829015103.GA28162@kroah.com>
     [not found]             ` <20060829031430.GA9820@flower.upol.cz>
2006-08-29  2:49               ` Greg KH
2006-08-29  4:19                 ` Oleg Verych
2006-08-29 15:46                 ` David Lang
2006-08-29 18:32                   ` Greg KH
2006-08-29 19:04                     ` Michael Buesch
2006-08-29 20:13                       ` Olaf Hering
2006-08-29 20:42                         ` David Lang
2006-08-29 20:52                           ` Greg KH
2006-08-30  5:44                           ` Olaf Hering
2006-08-30 17:52                             ` David Lang
2006-08-30 18:13                               ` Sven Luther [this message]
2006-08-30 18:20                                 ` David Lang
2006-08-30 19:15                                   ` Sven Luther
2006-08-30 19:34                                     ` David Lang
2006-08-30 20:57                                       ` Sven Luther
2006-08-30 21:11                                         ` David Lang
2006-08-31  1:16                                           ` Jim Crilly
2006-09-15 19:48                               ` Olaf Hering
2006-08-29 16:30           ` Michael Buesch
2006-08-29 13:13 ` Marcel Holtmann
2006-08-29 20:16   ` Greg KH
2006-08-30 13:49     ` Marcel Holtmann
     [not found] <6OXsW-4pW-7@gated-at.bofh.it>
     [not found] ` <6Peat-82q-17@gated-at.bofh.it>
     [not found]   ` <6PgFh-53l-7@gated-at.bofh.it>
     [not found]     ` <6Ph8l-61I-9@gated-at.bofh.it>
2006-08-29 22:10       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2006-04-18 23:41 Jon Masters
2006-04-18 23:01 ` David Lang
2006-04-19  0:15   ` Jon Masters
2006-04-18 23:41     ` David Lang
2006-04-19  1:07       ` Jon Masters
2006-04-19  9:07 ` Duncan Sands
2006-04-19 12:41   ` Jon Masters
2006-04-19 15:32     ` Duncan Sands
2006-04-19 15:45       ` Jon Masters
2006-07-29 19:05 ` Jon Masters

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=20060830181310.GA11213@powerlinux.fr \
    --to=sven.luther@wanadoo.fr \
    --cc=James.Bottomley@steeleye.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=dlang@digitalinsight.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=olaf@aepfle.de \
    --cc=olecom@flower.upol.cz \
    /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