From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>
Subject: network manager vs. missing firmware
Date: Tue, 13 Feb 2007 19:41:46 +0100 [thread overview]
Message-ID: <1171392106.10344.100.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi,
Just remembered this issue from last year's summit and figured I'd bring
it up again since we never made progress on it.
Is there any idea other than standardising on a new error code
-ENOFIRMWARE that can be returned from device up or association or
wherever makes sense for the driver. Or do we also mandate that it be
returned on device up, and for example never on module load? I think
it's mostly a question of documentation/driver acceptance policy/driver
review as well as a question of whether we can get a new error code into
the kernel or not.........
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2007-02-13 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 18:41 Johannes Berg [this message]
2007-02-13 19:23 ` network manager vs. missing firmware Dan Williams
2007-02-13 19:37 ` Johannes Berg
2007-02-13 19:43 ` Michael Wu
2007-02-13 20:13 ` Luis R. Rodriguez
2007-02-13 20:58 ` Dan Williams
2007-02-14 0:36 ` James Ketrenos
2007-02-14 2:47 ` Luis R. Rodriguez
2007-02-15 18:53 ` James Ketrenos
2007-02-14 19:24 ` Johannes Berg
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=1171392106.10344.100.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.