From: Stefan Rompf <stefan@loplof.de>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: State of the Union: Wireless
Date: Fri, 6 Jan 2006 13:48:05 +0100 [thread overview]
Message-ID: <200601061348.05803.stefan@loplof.de> (raw)
In-Reply-To: <20060106114620.GA23707@isilmar.linta.de>
Am Freitag 06 Januar 2006 12:46 schrieb Dominik Brodowski:
> From someone who has no idea at all (yet) about 802.11: why character
> device, and not sysfs or configfs files? Like
sysfs shares the main problem with wireless extensions: It configures one
value per file / per ioctl. Setting up a wireless card to associate or form
an IBSS network consists of multiple parameters, many requiring the card to
disasscociate.
With hardware like prism2 usb that gets "don't touch me now mode" for a while
after a join command is issued, current API requires a driver to delay
starting an association in order to wait if other config requests are issued
- an ugly hack.
I vote for netlink. It's a defined and tested interface and has all features
needed to set multiple values in one transaction.
Stefan
next prev parent reply other threads:[~2006-01-06 12:48 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
2006-01-06 12:48 ` Stefan Rompf [this message]
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=200601061348.05803.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=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).