From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: Jon Smirl <jonsmirl@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Errors when firmware is missing
Date: Sat, 7 Jul 2007 20:37:44 +0200 [thread overview]
Message-ID: <200707072037.44582.mb@bu3sch.de> (raw)
In-Reply-To: <468FD6B2.6000408@lwfinger.net>
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...
--
Greetings Michael.
next prev parent reply other threads:[~2007-07-07 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 16:27 Errors when firmware is missing Jon Smirl
2007-07-07 16:41 ` Johannes Berg
2007-07-07 17:24 ` Daniel Drake
2007-07-10 22:58 ` Johannes Berg
2007-07-07 21:34 ` Dan Williams
2007-07-10 22:56 ` Johannes Berg
2007-07-07 18:08 ` Larry Finger
2007-07-07 18:37 ` Michael Buesch [this message]
2007-07-07 21:33 ` Dan Williams
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=200707072037.44582.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jonsmirl@gmail.com \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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