From: Johannes Berg <johannes@sipsolutions.net>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: State of the Union: Wireless
Date: Fri, 06 Jan 2006 13:26:24 +0100 [thread overview]
Message-ID: <1136550384.4037.48.camel@localhost> (raw)
In-Reply-To: <20060106114620.GA23707@isilmar.linta.de>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
> From someone who has no idea at all (yet) about 802.11: why character
> device, and not sysfs or configfs files? Like
As Michael already said -- there's no real reason for that. We were just
brainstorming. The /dev idea seemed like a good plan at first, but then
it isn't fixed. What you suggested below does look useful too.
Coming back to the point Michael already raised: the overarching idea is
to get rid of the net_dev for the 'master' device, even if the
underlying hardware supports only a single virtual device (which might
then be created by the driver automatically)
I'll move the wiki pages a bit to accomodate different models, please
check in a few minutes.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2006-01-06 12:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 4:22 State of the Union: Wireless Jeff Garzik
2006-01-06 11:31 ` Johannes Berg
2006-01-06 11:46 ` Dominik Brodowski
2006-01-06 12:26 ` Johannes Berg [this message]
2006-01-06 12:48 ` Stefan Rompf
2006-01-06 12:53 ` Johannes Berg
2006-01-07 14:49 ` Denis Vlasenko
2006-01-10 13:18 ` Johannes Berg
2006-01-10 6:39 ` Denis Vlasenko
2006-01-10 8:36 ` Chase Venters
2006-01-10 10:41 ` Andreas Mohr
2006-01-11 2:05 ` Wireless: One small step towards a more perfect union...? John W. Linville
2006-01-11 5:17 ` David S. Miller
2006-01-11 8:37 ` Jeff Garzik
2006-01-11 13:19 ` Bas Vermeulen
2006-01-11 22:28 ` Daniel Drake
2006-01-11 22:37 ` Jeff Garzik
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=1136550384.4037.48.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).