Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 ethX reset I presume that this is sufficient, and I can drop this thread (except the comment cleanup patch)? John -- John W. Linville [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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: [EMAIL PROTECTED]:/sys/devices/pci:00/:00:1e.0/:02:02.0# ls broken_parity_status config irq power/ subsystem@ uevent bus@ device local_cpus resource subsystem_device vendor class enable modaliasresource0 subsystem_vendor [EMAIL PROTECTED]:/sys/devices/pci:00/:00:1e.0/: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 - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 + replug the device, at which point the driver init routine runs again. Can we document how to do that? I've wanted to synthesize such things before, and I couldn't quite reason how. just load fakephp then do echo -n 0 /sys/bus/pci/slots/:04:02.1/power this hotunplugs it (fake) then just do echo -n 1 /sys/bus/pci/slots/:04:02.0/power (or any other device on the 04 bus) and the kernel finds the 04:02.1 device again... - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 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: [EMAIL PROTECTED]:/sys/devices/pci:00/:00:1e.0/:02:02.0# ls /sys/bus/pci/slots/:04:02.1 need to go there via bus/pci/slots - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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? Is bcm43xx able to get the MAC address before the firmware is loaded? 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 ;) ) Last time I checked, if the MAC address is only discovered after the interface is created (as would be the case with ipw loading firmware on ifconfig up, I think), interface renaming does not work. -- Greetings Michael. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 address for ipw2100/ipw2200 until the firmware is loaded. Daniel - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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, and it can't be loaded by
userspace loader when userspace is not running.
False, initramfs...
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?
Probably not. This (very dirty) hack implements that (with some level
of success -- ifconfig down/ifconfig up is enough to get wireless
working).
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
Pavel
--- clean-mm/drivers/net/wireless/ipw2200.c 2006-07-11 15:22:50.0
+0200
+++ linux-mm/drivers/net/wireless/ipw2200.c 2006-07-11 14:38:01.0
+0200
@@ -97,6 +97,7 @@
static int bt_coexist = 0;
static int hwcrypto = 0;
static int roaming = 1;
+static int needs_reinit = 1;
static const char ipw_modes[] = {
'a', 'b', 'g', '?'
};
@@ -10013,10 +10014,20 @@
sys_config-silence_threshold = 0x1e;
}
+static int ipw_pci_suspend(struct pci_dev *pdev, pm_message_t state);
+static int ipw_pci_resume(struct pci_dev *pdev);
+
static int ipw_net_open(struct net_device *dev)
{
struct ipw_priv *priv = ieee80211_priv(dev);
IPW_DEBUG_INFO(dev-open\n);
+
+ if (needs_reinit) {
+ printk(ipw: Delayed loading the firmware\n);
+ ipw_pci_suspend(priv-pci_dev, PMSG_FREEZE);
+ ipw_pci_resume(priv-pci_dev);
+ }
+
/* we should be verifying the device is ready to be opened */
mutex_lock(priv-mutex);
if (!(priv-status STATUS_RF_KILL_MASK)
@@ -11295,7 +11306,8 @@
if (ipw_up(priv)) {
mutex_unlock(priv-mutex);
- return -EIO;
+ needs_reinit = 1;
+ return 0;
}
mutex_unlock(priv-mutex);
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 PROTECTED] Phone: (650) 506-8127 - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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... - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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. 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. Cheers, Auke - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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, 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. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 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. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 runs again. Can we document how to do that? I've wanted to synthesize such things before, and I couldn't quite reason how. In my case, I had RHEL4 module-init-tools that don't wait for modprobe, so I had to compile in scsi and qla2x00, but the qla2x00 needs firmware, and it's too early...etc. Joel -- Baby, even the losers Get luck sometimes. Even the losers Keep a little bit of pride. Joel Becker Principal Software Developer Oracle E-mail: [EMAIL PROTECTED] Phone: (650) 506-8127 - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 userspace is not running. False, initramfs... 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? -- Greetings Michael. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [patch] do not allow IPW_2100=Y or IPW_2200=Y
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 line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
