From: Pavel Machek <pavel@ucw.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: David Miller <davem@davemloft.net>,
auke-jan.h.kok@intel.com, jgarzik@pobox.com, yi.zhu@intel.com,
jketreno@linux.intel.com, netdev@vger.kernel.org,
linville@tuxdriver.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
Date: Tue, 11 Jul 2006 13:27:21 +0200 [thread overview]
Message-ID: <20060711112721.GA1618@elf.ucw.cz> (raw)
In-Reply-To: <1152557518.4874.79.camel@laptopd505.fenrus.org>
Hi!
> > > >> Kconfig currently allows compiling IPW_2100 and IPW_2200 into kernel
> > > >> (not as a module). Unfortunately, such configuration does not work,
> > > >> because these drivers need a firmware, and it can't be loaded by
> > > >> userspace loader when userspace is not running.
> > > >
> > > > False, initramfs...
> > >
> > > which would warrant some extra documentation in Kconfig explaining that this
> > > driver needs initramfs with firmware for it to work when compiled in the
> > > kernel. A link to the ipw2x00 documentation might also help.
> >
> > Besides, the initramfs runs long after the driver init routine
> > runs which is when the firmware needs to be available.
>
> .. unless you use sysfs to do a fake hotunplug + replug the device, at
> which point the driver init routine runs again.
Ouch, nice trick. But how do I actually pull it up? There's nothing
that looks like allowing that in /sys:
root@amd:/sys/devices/pci0000:00/0000:00:1e.0/0000:02:02.0# ls
broken_parity_status config irq power/ subsystem@
uevent
bus@ device local_cpus resource subsystem_device
vendor
class enable modalias resource0 subsystem_vendor
root@amd:/sys/devices/pci0000:00/0000:00:1e.0/0000:02:02.0#
I tried going to bus/drivers/ and unbind/rebind ipw2200 driver; that
does not work. I tried echo 0 > enable; echo 1 > enable, but no trick,
either.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-07-11 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 15:20 [patch] do not allow IPW_2100=Y or IPW_2200=Y Pavel Machek
2006-07-10 17:53 ` Jeff Garzik
2006-07-10 18:29 ` Auke Kok
2006-07-10 18:47 ` David Miller
2006-07-10 18:51 ` Arjan van de Ven
2006-07-10 20:56 ` Joel Becker
2006-07-11 14:42 ` Arjan van de Ven
2006-07-11 21:53 ` Joel Becker
2006-07-11 11:27 ` Pavel Machek [this message]
2006-07-11 14:42 ` Arjan van de Ven
2006-07-10 21:05 ` Michael Buesch
2006-07-11 11:53 ` Daniel Drake
2006-07-11 20:39 ` Michael Buesch
2006-07-11 20:59 ` Daniel Drake
2006-07-11 13:32 ` Pavel Machek
2006-07-12 4:39 ` Zhu Yi
2006-07-27 14:43 ` John W. Linville
2006-07-11 13:34 ` [patch] cleanup // comments from ipw2200 Pavel Machek
2006-07-10 22:21 ` [patch] do not allow IPW_2100=Y or IPW_2200=Y Jan Engelhardt
[not found] <6x7TQ-87H-17@gated-at.bofh.it>
[not found] ` <6x8df-8wm-13@gated-at.bofh.it>
[not found] ` <6xbaZ-4NX-1@gated-at.bofh.it>
[not found] ` <6xyhj-5Fq-19@gated-at.bofh.it>
2006-07-12 20:56 ` Bodo Eggert
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=20060711112721.GA1618@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@infradead.org \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.com \
/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).