Linux wireless drivers development
 help / color / mirror / Atom feed
From: David Lamparter <dl@diac24.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Lamparter <lists@diac24.net>,
	Dan Williams <dcbw@redhat.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] {cfg,nl}80211 API
Date: Tue, 12 Jun 2007 15:15:00 +0200	[thread overview]
Message-ID: <20070612131458.GA6411@charon.n2.diac24.net> (raw)
In-Reply-To: <20070611230434.GA13221@charon.n2.diac24.net>

Hi,

just for fun, I created a graph of wext->nl80211 mappings:
http://git.spaceboyz.net/?p=nl80211/nl80211-meta.git;a=blob_plain;f=nl80211-map.png;hb=865687f294a84d7847ed7a05aa63de5cbb1a0c89
- wext stuff marked red means I have no idea what that ioctl does
- lines marked blue mean I'm not sure whether that's correct
- nl80211 cmds in lowercase and light green aren't outlined yet

So, what's left?
> - more PHY config stuff?
>   - TX power? Should be able to configure a lower value...
>   - antenna selection?
      - antenna diversity, as noted by Holger Schurig
- the entire regulatory stuff

For this, my first idea (included in that graph) would be to have a
GET_REGULATORY_CAPS command which returns whether the device has a fixed
list of regdomains or whether it can load anything. Depending on that,
either SELECT_REGDOMAIN or SET_CHANLIST can be used. For the chanlist,
there would be additional attributes specifying stuff like max power,
active scanning, etc.

Other new:
- {get,set}{mac,radio} for tx power (within regulatory limits), retry
  stuff, antennas?, etc.

What I totally missed is that there also is no rate configuration command
yet (!). Do we want that in SET_CHANNEL? (and rename it to SET_PHY?)

-David


  parent reply	other threads:[~2007-06-12 13:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 23:04 [RFC] {cfg,nl}80211 API David Lamparter
2007-06-12  9:15 ` Johannes Berg
2007-06-12 12:08   ` Dan Williams
2007-06-12 14:55     ` Tomas Winkler
2007-06-12  9:59 ` Holger Schurig
2007-06-12 13:15 ` David Lamparter [this message]
2007-06-12 13:58   ` Mark Powell
2007-06-12 16:45     ` Michael Wu
2007-06-12 17:01       ` Mark Powell
2007-06-13  6:46         ` Michael Wu
2007-06-13 13:25         ` David Lamparter
2007-06-13 16:08         ` Johannes Berg
2007-06-13 10:22 ` Johannes Berg
2007-06-13 13:18   ` [RFC] {cfg,nl}80211 API - 802.11j David Lamparter

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=20070612131458.GA6411@charon.n2.diac24.net \
    --to=dl@diac24.net \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@diac24.net \
    /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