netdev
[Top] [All Lists]

Re: [Prism54-devel] Re: [PATCH/RFC] set_rates support for prism54

To: Vladimir Kondratiev <vkondra@xxxxxxx>, netdev@xxxxxxxxxxx
Subject: Re: [Prism54-devel] Re: [PATCH/RFC] set_rates support for prism54
From: Denis Vlasenko <vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 15 Aug 2004 20:12:18 +0300
Cc: Margit Schubert-While <margitsw@xxxxxxxxxxx>, prism54-devel@xxxxxxxxxxx, mcgrof@xxxxxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx
In-reply-to: <200408151949.01351.vkondra@xxxxxxx>
References: <5.1.0.14.2.20040815145122.00afd708@xxxxxxxxxxxxxxx> <200408151910.25641.vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200408151949.01351.vkondra@xxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: KMail/1.5.4
On Sunday 15 August 2004 19:48, Vladimir Kondratiev wrote:
> I would not mix rates with modulation and other channel parameters.
> It looks better to bind frequency with parameters like modulation, channel
> width (10Mzh narrow channels in japan) etc. , into 'channel' number or
> (channel,band) tuple.

Consider need of being able to:

set_rates "1,2 5p,11p,22p" - i.e. "use PBCC modulation"
set_rates "1,2 5,11,22p" - "use standard CCK, and PBCC only for 22Mbit"

See? Very similar, but not the same.
So, how do you propose to express this?

This need is not imagined by me, it is very real for acx100
owners.

> For supported and optional rate, IE (info element) format may be the best
> choice.

I did not quite understand you, can you elaborate a bit?
--
vda


<Prev in Thread] Current Thread [Next in Thread>