From: Ben Greear <greearb@candelatech.com>
To: Michael Griepentrog <griepent@cs.wisc.edu>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Detect if phy is a/b/g/n?
Date: Fri, 24 Sep 2010 07:03:40 -0700 [thread overview]
Message-ID: <4C9CAFBC.3010702@candelatech.com> (raw)
In-Reply-To: <AANLkTinHY5LfzcQNvbVr6kY87Bjhy0TMYB8uU=k0ReZU@mail.gmail.com>
On 09/23/2010 03:22 PM, Michael Griepentrog wrote:
> There should also be a "HT TX/RX MCS rate indexes supported:" for n rates.
That is unique, so I can use that.
Next time someone is hacking on this, though, it would be nice for
a simple print-out of the various a/b/g/n modes supported!
Thanks,
Ben
>
> Mike
>
> On Thu, Sep 23, 2010 at 4:11 PM, Ben Greear<greearb@candelatech.com> wrote:
>> On 09/23/2010 01:35 PM, Luis R. Rodriguez wrote:
>>>
>>> On Thu, Sep 23, 2010 at 12:13 PM, Ben Greear<greearb@candelatech.com>
>>> wrote:
>>>>
>>>> Is there a way to determine what a/b/g/n modes a particular phy
>>>> supports? I tried 'iw phy', but I didn't see anything
>>>> obvious.
>>>
>>> 'iw list' Rates?
>>
>> Both a/b/g (ath5k) and /n (ath9k) show top speed of 54Mbps
>> on my systems.
>>
>> Ben
>>
>> --
>> Ben Greear<greearb@candelatech.com>
>> Candela Technologies Inc http://www.candelatech.com
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-09-24 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 19:13 Detect if phy is a/b/g/n? Ben Greear
2010-09-23 20:35 ` Luis R. Rodriguez
2010-09-23 21:11 ` Ben Greear
2010-09-23 22:22 ` Michael Griepentrog
2010-09-24 14:03 ` Ben Greear [this message]
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=4C9CAFBC.3010702@candelatech.com \
--to=greearb@candelatech.com \
--cc=griepent@cs.wisc.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.