Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <j@w1.fi>, linux-wireless@vger.kernel.org
Subject: Re: [RFC] nl80211: Add frequency configuration (including HT40)
Date: Wed, 26 Nov 2008 15:21:16 +0530	[thread overview]
Message-ID: <18733.7188.148730.783104@localhost.localdomain> (raw)
In-Reply-To: <1227688845.4613.53.camel@johannes.berg>

Johannes Berg wrote:
> On Wed, 2008-11-26 at 10:21 +0530, Sujith wrote:
> > Jouni Malinen wrote:
> > > + * @NL80211_ATTR_WIPHY_FREQ: frequency of the selected channel in MHz
> > > + * @NL80211_ATTR_WIPHY_SEC_CHAN_OFFSET: included with NL80211_ATTR_WIPHY_FREQ
> > > + *	if HT40 (40 MHz channels) are allowed:
> > > + *	NL80211_SEC_CHAN_BELOW = secondary channel is below the primary channel
> > > + *	NL80211_SEC_CHAN_ABOVE = secondary channel is above the primary channel
> > 
> > The driver needs to know if the selected channel is HT or not.
> 
> Can you explain what difference that makes? Is it for running the phy in
> pure legacy mode?

Yes, we calibrate the HW differently for HT/legacy.
Also, we have different rate tables for legacy/HT.
For HT20, it can reach 130 Mbps.

Sujith

  reply	other threads:[~2008-11-26  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 19:05 [RFC] nl80211: Add frequency configuration (including HT40) Jouni Malinen
2008-11-25 19:13 ` Johannes Berg
2008-11-26  7:52   ` Jouni Malinen
2008-11-26  4:51 ` Sujith
2008-11-26  7:55   ` Jouni Malinen
2008-11-26  8:05     ` Sujith
2008-11-26  8:40   ` Johannes Berg
2008-11-26  9:51     ` Sujith [this message]
2008-11-26  8:38 ` Jouni Malinen
2008-11-26 11:04   ` Johannes Berg
2008-11-26 13:14     ` Jouni Malinen
2008-11-26 13:38     ` Jouni Malinen
2008-11-26 13: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=18733.7188.148730.783104@localhost.localdomain \
    --to=m.sujith@gmail.com \
    --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