Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Michael Wu" <flamingice@sourmilk.net>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, "Jouni Malinen" <j@w1.fi>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: Mode/Channel/Bitrate API
Date: Wed, 17 Oct 2007 01:52:46 +0200	[thread overview]
Message-ID: <1ba2fa240710161652y4bbc29d0x289bac8e0e8f023b@mail.gmail.com> (raw)
In-Reply-To: <200710161640.54332.flamingice@sourmilk.net>

On 10/16/07, Michael Wu <flamingice@sourmilk.net> wrote:
> 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.
>
There are old AP  can be configured to use long preamble, so it shell
be configurable also in station.

> >  (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?
>
Will use short preamble ? In B/G it should use long preamble if not
configured otherwise.

> > Does anyone see problems with this?
> More specific examples of the API you have in mind would be helpful.
>
> Thanks,
> -Michael Wu
>
>

  reply	other threads:[~2007-10-16 23:52 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
2007-10-16 23:52   ` Tomas Winkler [this message]
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=1ba2fa240710161652y4bbc29d0x289bac8e0e8f023b@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=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