On Sat, 2007-07-07 at 20:37 +0200, Michael Buesch wrote: > On Saturday 07 July 2007 20:08:50 Larry Finger wrote: > > Jon Smirl wrote: > > > I have a new Broadcom 4318 adapter (which has exactly the same issues > > > with promiscuous mode). 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. > > > > If the firmware did not load correctly, the bcm43xx driver logs appropriate messages. This error > > would have been encountered and logged when the interface was brought up. Is that what you meant > > when you say that you received a log entry? The ifconfig error message is output by the user code, > > and is not controlled by any driver. > > Well it is. It's -ENOENT, which we return in the driver. > I'd like to return, -ENOFIRMWARE, but there's no such error. > So I selected the most sane error code (to me), which says > file not found... This should be what all drivers do; if, when setting IFF_UP, the device can't find firmware, it should return -ENOENT, which is the return code from request_firmware() when it fails to find the firmware. Thus, userspace can detect that firmware is missing and attempt to intelligently inform 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
