From: Pat Erley <pat-lkml@erley.org>
To: Richard Farina <sidhayn@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [DISCUSS] Implement non standard channel widths
Date: Tue, 04 Aug 2009 11:37:23 -0400 [thread overview]
Message-ID: <4A7855B3.1040007@erley.org> (raw)
In-Reply-To: <4A77AA0A.2030205@gmail.com>
Richard Farina wrote:
> Johannes Berg wrote:
>> Then, finally, I'd add a new channel type, NL80211_CHANNEL_TYPE_5MHZ.
>> Document it to imply that HT is being turned off, of course. Now this
>> bit should be really simple.
>>
>>
> But why? There is no reason mcs rates can't be used on 5/10 Mhz channels
> as far as I know. Bad enough these channels are running at half and
> quarter rates, if you can use mcs why not?
>
> Just my 0.02
>
> thanks,
> Rick Farina
My thought on this topic is: design everything so these COULD be supported,
but wait until someone tests/implements this functionality with a driver
and needs support for them. If I understood Johannes' description of things
correctly, if it was found that a driver could do mcs rates in other channel
widths, it'd be as simple as adding the values to the bitfields and that
driver testing/implementing that functionality.
What I guess it's come around to is:
1. Change the way the current functionality is implemented
2. Add additional values as it's added.
What I believe johannes was saying is, during the implementation of 5/10mhz
channels, disable ht/mcs modes up front, until someone shows/implements it.
Pat
next prev parent reply other threads:[~2009-08-04 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 23:55 [DISCUSS] Implement non standard channel widths Pat Erley
2009-08-02 8:31 ` Johannes Berg
2009-08-04 3:24 ` Richard Farina
2009-08-04 15:37 ` Pat Erley [this message]
2009-08-04 15:43 ` Luis R. Rodriguez
2009-08-04 6:15 ` Pat Erley
2009-08-04 6:55 ` Johannes Berg
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=4A7855B3.1040007@erley.org \
--to=pat-lkml@erley.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sidhayn@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;
as well as URLs for NNTP newsgroup(s).