linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: "ext Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: ext Grazvydas Ignotas <notasas@gmail.com>,
	Shahar Levi <shahar_levi@ti.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Kalle Valo <kvalo@adurom.com>
Subject: Re: [PATCH v4] wl1271: Change wl12xx Files Names
Date: Thu, 04 Nov 2010 23:52:35 +0200	[thread overview]
Message-ID: <1288907555.17643.14.camel@powerslave> (raw)
In-Reply-To: <AANLkTi=Luv2+5Hys2PcrH+G8jmc4vwz8PM0LFKm+fTt8@mail.gmail.com>

On Thu, 2010-11-04 at 22:48 +0100, ext Gábor Stefanik wrote:
> On Thu, Nov 4, 2010 at 6:19 PM, Luciano Coelho <luciano.coelho@nokia.com> wrote:
> > On Thu, 2010-11-04 at 17:37 +0100, ext Grazvydas Ignotas wrote:
> >> On Thu, Nov 4, 2010 at 5:07 PM, Shahar Levi <shahar_levi@ti.com> wrote:
> >> > All files name prefix removed due to the fact that wl12xx driver supports
> >> > wl1271 and wl1273.
> >> > Also the definition in Kconfig and header files changed respectively.
> >> >
> >> > Signed-off-by: Shahar Levi <shahar_levi@ti.com>
> >>
> >> Hmh the name 'wl12xx' kind of implies it covers 1251, while in fact
> >> wl1251 is completely separate driver.. At least the Kconfig help text
> >> should mention it doesn't cover wl1251 and users should use respective
> >> driver for wl1251.
> >
> > That's a good point.  We have discussed this before and this was the
> > best solution we found.  The wl12xx driver includes support for wl1271
> > and wl1273, so we considered calling it wl127x, but in the near future,
> > we'll have support for wl1281 and wl1283 as well.  So we have to use
> > wl12xx.
> >
> > At least in my opinion, it is kind of clear that if there is a separate
> > driver for wl1251, the user would use that one.  In any case, A note in
> > the Kconfig help text would definitely not hurt.
> >
> > Shahar, could you please change the text in the Kconfig so that it reads
> > something like this?
> >
> > "This module adds support for wireless adapters based on TI wl1271 and
> > TI wl1273 chipsets.  This module does *not* include support for wl1251.
> > For wl1251 support, use the separate homonymous driver instead."
> 
> 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.

-- 
Cheers,
Luca.


  reply	other threads:[~2010-11-04 21:51 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 [this message]
2010-11-07 10:07         ` Kalle Valo
2010-11-08  9:16           ` Luciano Coelho
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=1288907555.17643.14.camel@powerslave \
    --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).