Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-27 Thread John W. Linville
On Wed, Jul 12, 2006 at 12:39:58PM +0800, Zhu Yi wrote: On Tue, 2006-07-11 at 15:32 +0200, Pavel Machek wrote: Probably not. This (very dirty) hack implements that (with some level of success -- ifconfig down/ifconfig up is enough to get wireless working). You just need to $ iwpriv

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Pavel Machek
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,

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Arjan van de Ven
On Mon, 2006-07-10 at 13:56 -0700, Joel Becker wrote: On Mon, Jul 10, 2006 at 08:51:58PM +0200, Arjan van de Ven wrote: 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 +

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Arjan van de Ven
On Tue, 2006-07-11 at 13:27 +0200, Pavel Machek wrote: 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

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Michael Buesch
On Tuesday 11 July 2006 13:53, you wrote: Michael Buesch wrote: Does the ipw driver _really_ need the firmware on insmod time? bcm43xx, for example, loads the firmware on ifconfig up time. If ipw really needs the firmware on insmod, is it possible to defer it to later at ifconfig up time?

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Daniel Drake
Michael Buesch wrote: Yes. We have a PROM that is readable without firmware. (And we actually do this and did it forever. So I don't know where your assumption comes from ;) ) It wasn't an assumption: I was stating something about the Intel cards. It is not possible to determine the MAC

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Pavel Machek
On Mon 2006-07-10 23:05:06, Michael Buesch wrote: On Monday 10 July 2006 19:53, you wrote: Pavel Machek wrote: 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,

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Joel Becker
On Tue, Jul 11, 2006 at 04:42:13PM +0200, Arjan van de Ven wrote: just load fakephp Thanks! I'd never heard of it :-) Joel -- The only way to get rid of a temptation is to yield to it. - Oscar Wilde Joel Becker Principal Software Developer Oracle E-mail: [EMAIL

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-11 Thread Zhu Yi
On Tue, 2006-07-11 at 15:32 +0200, Pavel Machek wrote: Probably not. This (very dirty) hack implements that (with some level of success -- ifconfig down/ifconfig up is enough to get wireless working). You just need to $ iwpriv ethX reset Thanks, -yi - To unsubscribe from this list: send the

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Jeff Garzik
Pavel Machek wrote: 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... -

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Auke Kok
Jeff Garzik wrote: Pavel Machek wrote: 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.

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread David Miller
From: Auke Kok [EMAIL PROTECTED] Date: Mon, 10 Jul 2006 11:29:30 -0700 Jeff Garzik wrote: Pavel Machek wrote: 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,

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Arjan van de Ven
On Mon, 2006-07-10 at 11:47 -0700, David Miller wrote: From: Auke Kok [EMAIL PROTECTED] Date: Mon, 10 Jul 2006 11:29:30 -0700 Jeff Garzik wrote: Pavel Machek wrote: Kconfig currently allows compiling IPW_2100 and IPW_2200 into kernel (not as a module). Unfortunately, such

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Joel Becker
On Mon, Jul 10, 2006 at 08:51:58PM +0200, Arjan van de Ven wrote: 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

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Michael Buesch
On Monday 10 July 2006 19:53, you wrote: Pavel Machek wrote: 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

Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y

2006-07-10 Thread Jan Engelhardt
Is there better way of creating N/m config option? config IPW2100 tristate Intel PRO/Wireless 2100 Network Connection - depends on NET_RADIO PCI + depends on NET_RADIO PCI MODULE_ONLY depends on NET_RADIO PCI m Jan Engelhardt -- - To unsubscribe from this list: send the