From: Johannes Berg <johannes@sipsolutions.net>
To: Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: PCI express card that does AP mode? (abit wlp-01?)
Date: Fri, 24 Jul 2009 18:24:35 +0200 [thread overview]
Message-ID: <1248452675.32151.31.camel@johannes.local> (raw)
In-Reply-To: <wfmy6u6opl.fsf@calligramme.charmers>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Fri, 2009-07-24 at 17:16 +0100, Jon Fairbairn wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> > I also added a short overview over the form factors on the page:
> > http://wireless.kernel.org/en/users/Devices/PCI.
>
> That's really good!
And quick too, thanks Pavel!
> (In the "asking for the moon on a stick" department, it would be handy
> to have a table somewhere with "supported features" and "form factor"
> dropdowns, so that I could have selected "AP" and "PCIe" and get the
> card I now have ;-)
I wondered about that, but the list really gets too wide, and it's
really a driver rather than device property whether it supports AP or
not.
Then of course, there's also band/11n streams/... information that you
might want.
I'm starting to think we should remove all the numbers (pci vendor,
product, subvendor, subsystem) in favour of more interesting information
like that.
However, as far as AP is concerned, how about we just add a little help
text that explains that you should look on the Drivers page to see
whether it supports what you need, and then select by driver? We could
make the driver table better to allow filtering.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-24 16:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 8:02 PCI express card that does AP mode? (abit wlp-01?) Jon Fairbairn
2009-07-16 16:14 ` Luis R. Rodriguez
2009-07-16 16:39 ` Jon Fairbairn
2009-07-16 16:48 ` Luis R. Rodriguez
2009-07-16 17:01 ` Gábor Stefanik
2009-07-16 23:50 ` Jouni Malinen
2009-07-16 23:59 ` Luis R. Rodriguez
2009-07-17 9:57 ` Jon Fairbairn
2009-07-16 16:36 ` Pavel Roskin
2009-07-16 17:01 ` Jon Fairbairn
2009-07-16 20:20 ` Pavel Roskin
2009-07-17 9:58 ` Jon Fairbairn
2009-07-24 7:39 ` Jon Fairbairn
2009-07-24 15:23 ` Pavel Roskin
2009-07-24 15:29 ` Johannes Berg
2009-07-24 15:43 ` Jon Fairbairn
2009-07-24 15:47 ` Johannes Berg
2009-07-24 15:52 ` Pavel Roskin
2009-07-24 15:59 ` Johannes Berg
2009-07-24 16:04 ` Pavel Roskin
2009-07-24 16:09 ` Johannes Berg
2009-07-24 16:16 ` Jon Fairbairn
2009-07-24 16:24 ` Johannes Berg [this message]
2009-07-25 7:46 ` Jon Fairbairn
2009-07-24 16:07 ` Larry Finger
2009-07-24 15:40 ` Jon Fairbairn
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=1248452675.32151.31.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=jon.fairbairn@cl.cam.ac.uk \
--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;
as well as URLs for NNTP newsgroup(s).