Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Errors when firmware is missing
Date: Sat, 07 Jul 2007 18:41:15 +0200	[thread overview]
Message-ID: <1183826476.3779.42.camel@johannes.berg> (raw)
In-Reply-To: <9e4733910707070927l37bdf79cpd1fc672909fb0bb3@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

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.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-07-07 16:40 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 [this message]
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
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=1183826476.3779.42.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=jonsmirl@gmail.com \
    --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