From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Andriy Korud <a.korud@vector.com.pl>
Cc: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>,
Steve Hill <steve@nexusuk.org>, Netdev <netdev@oss.sgi.com>,
Jean Tourrilhes <jt@bougret.hpl.hp.com>,
"Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, prism54-users@prism54.org,
prism54-devel@prism54.org
Subject: Re: [Prism54-devel] Re: [Prism54-users] Open hardware wireless cards
Date: Thu, 6 Jan 2005 10:16:16 -0500 [thread overview]
Message-ID: <20050106151616.GC30311@csclub.uwaterloo.ca> (raw)
In-Reply-To: <60E856FD577CC04BA3727AF4122D3F161134B8@3bit.vector.com.pl>
On Wed, Jan 05, 2005 at 11:34:02PM +0100, Andriy Korud wrote:
> Sorry, as I know (no more details - NDA, sorry) some manufacturers are developing (and planning to continue) FullMAC 802.11g (and further) chipsets and also they are offering Linux drivers (however had no chance to test yet).
>
> But from my point of view, SoftMAC cards are better sometimes - you have more control from drivers and can implement some interesting features (for example, madwifi Linux driver with MAC layer ported from xBSD).
>
> Any thoughts why we should prefer FullMAC cards over SoftMAC (except CPU usage, of course)?
Embedded systems with low end cpus (to make less heat and use less
power) would prefer anything that uses less cpu and can be done in
dedicated (and usually simpler than the cpu) hardware. Of course the
windows laptop and desktop market probably far outsells the embedded
market, for now at least.
Len Sorensen
prev parent reply other threads:[~2005-01-06 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 22:34 Andriy Korud
2005-01-06 15:16 ` Lennart Sorensen [this message]
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=20050106151616.GC30311@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=a.korud@vector.com.pl \
--cc=jgarzik@pobox.com \
--cc=jt@bougret.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.org \
--cc=prism54-users@prism54.org \
--cc=steve@nexusuk.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
all inboxes | Powered by JetHome®