Search Linux Wireless

Re: Errors when firmware is missing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2007-07-07 at 18:41 +0200, Johannes Berg wrote:
> On Sat, 2007-07-07 at 12:27 -0400, Jon Smirl wrote:
> > I have a new Broadcom 4318 adapter (which has exactly the same issues
> > with promiscuous mode).
> 
> Huh? That's really weird.
> 
> > I didn't have the right firmware down for it
> > and I received this error message when I did "ifconfig wlan up"
> > SIOCSIFFLAGS: No such file or directory.  This is not the most user
> > friendly error message, but I did receive a log entry.
> > 
> > I tried the same thing with the zd1211. In this case the wlan0 device
> > didn't get created.
> > 
> > Does it make sense to specify consistent behavior when the firmware is missing?
> 
> It does, and I believe we've talked about it at the wireless summits,
> but I'm not aware that we've reached a conclusion. It would probably be
> nice to have an error message -EFIRMWARE or something; that for zd1211
> no device is created is probably counter-productive, that way userspace
> will never know that a wireless adapter is plugged in.

Drivers should be returning -ENOENT (the error from request_firmware()
when the firmware isn't found) when userspace sets IFF_UP on the device,
so that userspace has the faintest hope of intelligently informing the
user.

Dan


-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux