From: "Fabio Comolli" <fabio.comolli@gmail.com>
To: "Matthew Wilcox" <matthew@wil.cx>
Cc: "James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
sam@ravnborg.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Possible bug in SCSI Kconfig
Date: Wed, 22 Oct 2008 21:45:15 +0200 [thread overview]
Message-ID: <b637ec0b0810221245p98f5837j58fdc505cf4fa131@mail.gmail.com> (raw)
In-Reply-To: <20081022193458.GJ26094@parisc-linux.org>
Hi.
On Wed, Oct 22, 2008 at 9:34 PM, Matthew Wilcox <matthew@wil.cx> wrote:
> On Wed, Oct 22, 2008 at 09:31:51PM +0200, Fabio Comolli wrote:
>> Unfortunately this is not an option because of ipw2200. I don't use
>> initrd and if I turn off CONFIG_MODULES the kernel hangs forever
>> requesting the firmware.
>
> Have you investigated CONFIG_EXTRA_FIRMWARE?
Wow! You made my day:
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmr
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200 0000:06:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
firmware: using built-in firmware ipw2200-bss.fw
Thanks!
>
> --
> Matthew Wilcox Intel Open Source Technology Centre
> "Bill, look, we understand that you're interested in selling us this
> operating system, but compare it to ours. We can't possibly take such
> a retrograde step."
>
next prev parent reply other threads:[~2008-10-22 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 16:29 Fabio Comolli
2008-10-22 18:35 ` Stefan Richter
2008-10-22 19:29 ` Fabio Comolli
2008-10-22 19:05 ` James Bottomley
2008-10-22 19:25 ` Fabio Comolli
2008-10-22 19:26 ` Matthew Wilcox
2008-10-22 19:31 ` Fabio Comolli
2008-10-22 19:34 ` Matthew Wilcox
2008-10-22 19:45 ` Fabio Comolli [this message]
2008-10-22 19:44 ` James Bottomley
2008-10-22 19:48 ` Fabio Comolli
2008-10-23 17:30 ` Stefan Richter
2008-10-23 17:39 ` Matthew Wilcox
2008-10-23 18:59 ` Stefan Richter
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=b637ec0b0810221245p98f5837j58fdc505cf4fa131@mail.gmail.com \
--to=fabio.comolli@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®