All of lore.kernel.org
 help / color / mirror / Atom feed
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 --]

  reply	other threads:[~2006-01-06 12:26 UTC|newest]

Thread overview: 34+ 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   ` [Acx100-devel] " Andreas Mohr
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
     [not found] <5rRp0-4X1-3@gated-at.bofh.it>
2006-01-06  5:39 ` State of the Union: Wireless Robert Hancock
2006-01-06  6:42   ` Randy.Dunlap
2006-01-06 10:26   ` Alistair John Strachan
     [not found] <1136541243.4037.18.camel@localhost>
2006-01-06 11:00 ` [Bcm43xx-dev] [Fwd: State of the Union: Wireless] Michael Buesch
2006-01-06 16:04   ` State of the Union: Wireless Mike Kershaw
  -- strict thread matches above, loose matches on Subject: below --
2006-01-10 12:38 Tim Tassonis
2006-01-10 12:53 ` Adrian Bunk
2006-01-10 13:34   ` Tim Tassonis
2006-01-10 14:13     ` Adrian Bunk
2006-01-10 16:07       ` Tim Tassonis
2006-01-10 16:31         ` Adrian Bunk
2006-01-10 16:17       ` Tim Tassonis
2006-01-11 20:37       ` Pavel Machek
2006-01-14  9:43         ` Jeff Garzik
2006-01-10 14:16 ` Chase Venters
     [not found] ` <mailman.1136898727.7233.linux-kernel2news@redhat.com>
2006-01-11  0:03   ` Pete Zaitcev
2006-01-11  0:29     ` Adrian Bunk

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 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.