Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Michael Wu" <flamingice@sourmilk.net>,
	linux-wireless@vger.kernel.org, "Jouni Malinen" <j@w1.fi>
Subject: Re: Mode/Channel/Bitrate API
Date: Wed, 17 Oct 2007 10:15:03 -0400	[thread overview]
Message-ID: <43e72e890710170715ibeee99eja865dc3291e7e37d@mail.gmail.com> (raw)
In-Reply-To: <1192608587.8841.2.camel@johannes.berg>

On 10/17/07, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Tue, 2007-10-16 at 16:40 -0400, Michael Wu 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.
>
> Yeah but it doesn't help when the user wants to enable/disable certain
> channels or the regulatory code needs to, so it seems we need to go with
> a list.

The regulatory work can just iterate over the currently established
channels for each wiphy. Who defines those or how is not important to
the regulatory work. I'm not sure why the range approach would not
work here. A card usually works on a range of frequencies anyway.

  Luis

  reply	other threads:[~2007-10-17 14:15 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
2007-10-17  8:09   ` Johannes Berg
2007-10-17 14:15     ` Luis R. Rodriguez [this message]
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=43e72e890710170715ibeee99eja865dc3291e7e37d@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=flamingice@sourmilk.net \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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