From: Michael Wu <flamingice@sourmilk.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: Mode/Channel/Bitrate API
Date: Tue, 16 Oct 2007 16:40:49 -0400 [thread overview]
Message-ID: <200710161640.54332.flamingice@sourmilk.net> (raw)
In-Reply-To: <1192222110.4770.81.camel@johannes.berg>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Friday 12 October 2007 16:48:30 Johannes Berg wrote:
> (a) the driver registers which channel center frequencies it can
> operate with, it could in theory just be a range (e.g. 2400-2500
> MHz) or more practically be list of center frequencies.
List would be best, but..
> Just
> contains frequencies and possibly hardware dependent values for the
> frequency. This is done in "bands", something like
> FREQUENCY_BAND_2_4GHZ and FREQUENCY_BAND_5GHZ, "bands" replace the
> current "modes".
Being able to just register frequency bands would work for many (but not all)
drivers out there and would be more convenient than listing everything.
> (b) additionally, the driver registers as flags
> - whether it can support G mode short slot operation
> - whether it can receive B mode short barker preambles
> (both of which are only relevant if it supports 2.4 GHz operation)
I haven't seen any softmac 11b hardware that doesn't support receiving short
preamble yet.
> (d) now, selecting a channel by frequency is unique, but we need to
> give new options to select short slot, short preamble and allowed
> bitrates.
Short preamble? What would the hardware do with this bit?
> Does anyone see problems with this?
More specific examples of the API you have in mind would be helpful.
Thanks,
-Michael Wu
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-10-16 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:48 Mode/Channel/Bitrate API Johannes Berg
2007-10-16 20:40 ` Michael Wu [this message]
2007-10-16 23:52 ` Tomas Winkler
2007-10-17 8:09 ` Johannes Berg
2007-10-17 14:15 ` Luis R. Rodriguez
2007-10-18 12:40 ` Johannes Berg
2007-10-18 14:49 ` Luis R. Rodriguez
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=200710161640.54332.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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