From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Kalle Valo <kvalo@adurom.com>
Cc: "ext Gábor Stefanik" <netrolller.3d@gmail.com>,
"ext Grazvydas Ignotas" <notasas@gmail.com>,
"Shahar Levi" <shahar_levi@ti.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4] wl1271: Change wl12xx Files Names
Date: Mon, 08 Nov 2010 11:16:08 +0200 [thread overview]
Message-ID: <1289207768.8423.15.camel@chilepepper> (raw)
In-Reply-To: <87oca1zbt0.fsf@purkki.adurom.net>
On Sun, 2010-11-07 at 11:07 +0100, ext Kalle Valo wrote:
> Luciano Coelho <luciano.coelho@nokia.com> writes:
>
> >> What about wl1251 vs. wl12agn (or wl12bgn if no .11a support), like iwlwifi?
> >
> > Hmmm... wl1251 supports bg. wl12xx supports abgn. I don't really see
> > the logic in this? What difference does it make comparing to calling it
> > wl12xx? From wl12agn the user still doesn't know whether wl1251 is
> > supported or not.
>
> Just to confuse even more: TI wl1253 (the chip) supports 11a and it
> would be easy to add wl1253 (the chip) support to wl1251 (the driver).
> I just haven't seen any linux devices using wl1253 yet.
Oh, I didn't even know that wl1253 even existed. :) But yeah, it
complicates things even more indeed.
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-11-08 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 15:07 [PATCH v4] wl1271: Change wl12xx Files Names Shahar Levi
2010-11-04 16:37 ` Grazvydas Ignotas
2010-11-04 17:19 ` Luciano Coelho
2010-11-04 21:48 ` Gábor Stefanik
2010-11-04 21:52 ` Luciano Coelho
2010-11-07 10:07 ` Kalle Valo
2010-11-08 9:16 ` Luciano Coelho [this message]
2010-11-17 18:08 ` Gabay, Benzy
2010-11-17 18:48 ` Luciano Coelho
2010-11-18 2:13 ` Gabay, Benzy
2010-11-18 5:18 ` Krakowski, Oz
2010-11-18 6:21 ` Luciano Coelho
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=1289207768.8423.15.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=notasas@gmail.com \
--cc=shahar_levi@ti.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).