From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 6/7] wireless: update mac80211 kconfig entry
Date: Tue, 1 Sep 2009 10:38:23 -0700 [thread overview]
Message-ID: <20090901173822.GG8261@mosca> (raw)
In-Reply-To: <69e28c910909011028i25fba508t9e68fb24168193eb@mail.gmail.com>
On Tue, Sep 01, 2009 at 10:28:35AM -0700, Gábor Stefanik wrote:
> On Tue, Sep 1, 2009 at 7:18 PM, Luis R. Rodriguez<lrodriguez@atheros.com> wrote:
> > On Tue, Sep 01, 2009 at 09:33:00AM -0700, Jouni Malinen wrote:
> >> On Tue, Sep 01, 2009 at 08:54:25AM -0700, Luis R. Rodriguez wrote:
> >> > + SoftMAC devices. SoftMAC devices allow for a finer control of the
> >>
> >> Again, I don't really like the term "SoftMAC" here..
> >
> > What's a better term?
> >
>
> "Software-based", "Software-MAC", "Software-defined", or anything that
> neither implies that the stack is designed for PrismGT (the
> capitalization "SoftMAC" comes from Intersil AFAIK), nor allows
> confusion with ieee80211softmac (which could result if we write it
> with all small letters as "softmac").
Indeed, I picked up 'SoftMAC' and 'FullMAC' terminology from the prism54 days
after they decided to move in that direction as others were or already had. For
better or for worse I have been using 'SoftMAC' throughout wireless.kernel.org
documentation to distinguish between 'FullMAC' cards. I really have not been
able to find any other suitable replacements, are there legal reasons to not use
such terms?
I thought 'mac80211' name was brilliant as it highlighted the main focus for the
module, to focus on the MAC frame processing, I just cannot think of any
description for it other than something to support SoftMAC cards.
Luis
next prev parent reply other threads:[~2009-09-01 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 15:54 [PATCH v2 6/7] wireless: update mac80211 kconfig entry Luis R. Rodriguez
2009-09-01 16:33 ` Jouni Malinen
2009-09-01 17:17 ` Gábor Stefanik
2009-09-01 17:18 ` Luis R. Rodriguez
[not found] ` <69e28c910909011028i25fba508t9e68fb24168193eb@mail.gmail.com>
2009-09-01 17:38 ` Luis R. Rodriguez [this message]
2009-09-01 17:47 ` Gábor Stefanik
2009-09-01 18:01 ` Luis R. Rodriguez
2009-09-01 18:07 ` John W. Linville
2009-09-01 19:07 ` Johannes Berg
2009-09-01 19:19 ` Luis R. Rodriguez
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=20090901173822.GG8261@mosca \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox