From: Denis Vlasenko <vda@ilport.com.ua>
To: Alejandro Bonilla Beeche <abonilla@linuxwireless.org>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Rob Landley <rob@landley.net>,
kronos@kronoz.cjb.net, Keenan Pepper <keenanpepper@gmail.com>,
linux-kernel@vger.kernel.org, jketreno@linux.intel.com
Subject: Re: ipw2200 only works as a module?
Date: Mon, 24 Oct 2005 09:17:35 +0300 [thread overview]
Message-ID: <200510240917.35757.vda@ilport.com.ua> (raw)
In-Reply-To: <435C0C5E.5000709@linuxwireless.org>
On Monday 24 October 2005 01:19, Alejandro Bonilla Beeche wrote:
> >>>>With CONFIG_IPW2200=y I get:
> >>>>
> >>>>ipw2200: ipw-2.2-boot.fw load failed: Reason -2
> >>>>ipw2200: Unable to load firmware: 0xFFFFFFFE
> >>>>
> >>>>but with CONFIG_IPW2200=m it works fine. If it doesn't work when built
> >>>>into the kernel, why even give people the option?
because we want allyesconfig to compile.
> I have seen this before with users using FC or RH. They end up
> increasing the timeout of the hotplug event and then it all works. But
> then again, it only occurs for what I have seen with FC users. Dunno Why.
Firmware-loaded-by-hotplug is a necessary compromise in non-GPL world.
Ideally, firmware can be GPLed too and be included in the module
(u32 firmware_image[NNN]).
With closed firmwares, you should use modules (or wait until kernel will
have usable hotplug before root fs is mounted).
--
vda
prev parent reply other threads:[~2005-10-24 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 15:22 ipw2200 only works as a module? Keenan Pepper
2005-09-26 17:07 ` Bharath Ramesh
2005-09-26 17:12 ` Luca
2005-09-27 5:11 ` Alejandro Bonilla
2005-10-19 21:35 ` Rob Landley
2005-10-22 22:50 ` Alistair John Strachan
2005-10-23 22:19 ` Alejandro Bonilla Beeche
2005-10-24 6:17 ` Denis Vlasenko [this message]
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=200510240917.35757.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=abonilla@linuxwireless.org \
--cc=jketreno@linux.intel.com \
--cc=keenanpepper@gmail.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=s0348365@sms.ed.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.