From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 802.11n PCI-E 300Mbps with AP mode?
Date: Sat, 16 Jul 2011 02:28:01 +0200 [thread overview]
Message-ID: <4E20DB11.7060604@ionic.de> (raw)
In-Reply-To: <CAN0CFw3tkNkHE+RtzxV1k3kRDT+rSnxLE50qas4h0h1ZnasRaw@mail.gmail.com>
* On 15.07.2011 04:54 AM, Grant wrote:
> I don't feel anything as long as they're a few feet away. I tried a
> Bluetooth headset a few times and it was good for an instant headache.
> Too bad cause that would have been cool. Anyway, maybe I'm sensitive
> to the 2.4Ghz band. I don't know.
Hum, given that, are you actually sure you want to use WLAN? Even cards
transmit data and especially with laptops, you've got no other choice
but to stay close to it.
> I read in the reviews that people are achieving 300Mbps so I don't
> think the throughput is affected, but what is the functional
> difference between N and Draft-N?
I'm not sure if this is entirely correct, so anyone is invited to
correct me if I'm giving false information now. As far as I know, it's
impossible to say whether there are functional differences between
draft-n and n. Draft-n just means that the card was assembled/developed
when 802.11n was still a draft and no official standard yet. I don't
know how much the draft changed in process to ratification, but I GUESS
the changes are minimal, if even existent. So I'd rather see that as an
age indicator rather than functional delimiter. You can never be totally
sure though...
Best regards,
Mihai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4369 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110716/503d31f1/attachment.bin
next prev parent reply other threads:[~2011-07-16 0:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 22:10 [ath9k-devel] 802.11n PCI-E 300Mbps with AP mode? Grant
2011-07-12 23:23 ` Adrian Chadd
2011-07-13 0:26 ` Galen
2011-07-13 1:20 ` Grant
2011-07-13 1:55 ` Adrian Chadd
2011-07-13 23:42 ` Grant
2011-07-13 23:58 ` Mihai Moldovan
2011-07-14 4:39 ` Adrian Chadd
2011-07-14 0:00 ` Adrian Chadd
2011-07-14 4:18 ` Alex Hacker
2011-07-14 13:23 ` Galen
2011-07-14 18:56 ` Grant
2011-07-14 20:27 ` Mihai Moldovan
2011-07-15 2:35 ` Grant
2011-07-16 0:04 ` Mihai Moldovan
2011-07-16 18:47 ` Grant
2011-07-16 20:14 ` Mihai Moldovan
2011-07-13 15:22 ` Galen
2011-07-13 17:46 ` Grant
2011-07-13 19:55 ` Grant
2011-07-13 20:29 ` Daniel Smith
2011-07-14 18:54 ` Grant
2011-07-14 20:44 ` Mihai Moldovan
2011-07-15 2:54 ` Grant
2011-07-16 0:28 ` Mihai Moldovan [this message]
2011-07-16 19:54 ` Grant
2011-07-16 20:16 ` Mihai Moldovan
2011-07-17 1:58 ` Adrian Chadd
2011-07-17 2:10 ` Mihai Moldovan
2011-07-17 3:01 ` Adrian Chadd
2011-07-17 16:34 ` Grant
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=4E20DB11.7060604@ionic.de \
--to=ionic@ionic.de \
--cc=ath9k-devel@lists.ath9k.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 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.