From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev <netdev@vger.kernel.org>, Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [RFC] add nl80211
Date: Thu, 24 Aug 2006 17:20:46 +0200 [thread overview]
Message-ID: <1156432846.10283.6.camel@ux156> (raw)
In-Reply-To: <20060824143634.GM3470@postel.suug.ch>
On Thu, 2006-08-24 at 16:36 +0200, Thomas Graf wrote:
> Might want to put this in a header so userspace can see the limit.
Good point, thanks.
> In your case I'd call it GET_CMDLIST and NEW_CMDLIST which
> means you request a command list with GET_CMDLIST and
> receive the answer with a CMD_NEWLIST message.
Yeah, ok, I think I understood this now :)
> I'd just use the command id as attribute type:
>
> NLA_PUT_FLAG(msg, NL80211_CMD_GET_COMMANDS);
> NLA_PUT_FLAG(msg, NL80211_CMD_GET_WIPHYS);
> ....
>
> This makes checking avaibility of a command as easy as
> accessing an array for userspace.
Good point. However, userspace will need to be aware to parse this with
the max_cmd instead of max_attr :)
> > + err = genlmsg_end(msg, hdr);
> > + if (err)
> > + goto msg_free;
>
> genlmsg_end() can't fail, it just returns skb->len which
> is only of importance while dumping to see if there is
> still more to dump or not.
Whoops :)
> You might want to send out notifications for various events such as the
> additiona and deletion of virtual interfaces etc.
Yeah, I'm not sure how to do that yet, maybe have exported functions.
Currently, d80211 can also create virtual interfaces via sysfs so...
johannes
next prev parent reply other threads:[~2006-08-24 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 13:52 [RFC] add nl80211 Johannes Berg
2006-08-22 15:09 ` Johannes Berg
2006-08-23 9:40 ` Johannes Berg
2006-08-24 13:32 ` Jiri Benc
2006-08-24 14:15 ` Johannes Berg
2006-08-24 14:36 ` Thomas Graf
2006-08-24 15:20 ` Johannes Berg [this message]
2006-08-24 16:07 ` Johannes Berg
2006-08-24 17:27 ` Thomas Graf
2006-08-25 9:04 ` Johannes Berg
2006-08-25 10:30 ` Thomas Graf
2006-08-25 10:38 ` Johannes Berg
2006-08-25 11:01 ` [RFC take3] " 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=1156432846.10283.6.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).