netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Saillard <luc@saillard.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Jiri Benc <jbenc@suse.cz>, Michael Buesch <mbuesch@freenet.de>,
	linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	NetDev <netdev@vger.kernel.org>
Subject: Re: Broadcom 43xx first results
Date: Tue, 6 Dec 2005 11:23:40 +0100	[thread overview]
Message-ID: <20051206102340.GC24486@sd291.sivit.org> (raw)
In-Reply-To: <D76B7270-C6A7-4068-9FDD-4C8B9F491F62@mac.com>

On Tue, Dec 06, 2005 at 04:26:50AM -0500, Kyle Moffett wrote:
> On Dec 05, 2005, at 15:42, Jiri Benc wrote:
> >On Mon, 5 Dec 2005 21:23:42 +0100, Michael Buesch wrote:
> >>This is __not__ "yet another stack". It is an _extension_.  It is  
> >>all about management frames, which the in-kernel code does not  
> >>manage.
> >
> >But this code should be part of the stack, as nearly every driver  
> >needs it.
> 
> WRONG.  More than half the currently Linux-compatible wireless cards  
> handle the wireless management packets in hardware, such that they're  
> little more complicated than a basic ethernet device with a channel,  
> an ESSID, and a list of MACs/APs.
> 
 
I do not want to enter in this flamewar, but the current driver i'm working
on (marvell libertas chipset) need management frames in software. But to
reduce cost, i think that lower chipset try to put the most in the host and
not in the chipset. Marvell build the chipset around a ARM cpu so i think one
day i can do it in hardware but for now i need to choose a ieee802.11 stack.
I've began to used the in kernel solution with my own functions to
send and received this frame. But i hope we will find a technical solution
that please everyone. I'll try to see if the softmac layer written for
broadcom driver can be used for my project.

Luc

  reply	other threads:[~2005-12-06 10:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Eiyw4-0003Ab-FW@www1.emo.freenet-rz.de>
2005-12-05 18:00 ` Broadcom 43xx first results Jiri Benc
2005-12-05 18:14   ` Michael Renzmann
2005-12-05 18:46     ` Jeff Garzik
2005-12-05 18:49       ` Jiri Benc
2005-12-05 18:54         ` Jeff Garzik
2005-12-05 19:11           ` Jiri Benc
2005-12-06  7:17       ` Michael Renzmann
     [not found]   ` <20051205190038.04b7b7c1-IhiK2ZEFs2oCVLCxKZUutA@public.gmane.org>
2005-12-05 18:38     ` Joseph Jezak
2005-12-05 18:55       ` Jiri Benc
2005-12-05 19:08         ` Jeff Garzik
2005-12-05 19:18           ` Jiri Benc
2005-12-05 19:53           ` Dave Jones
2005-12-05 20:09             ` Jeff Garzik
2005-12-06 15:10             ` Harald Welte
2005-12-06 19:05               ` Jeff Garzik
2005-12-07  7:16                 ` Harald Welte
2005-12-06 23:19               ` David S. Miller
2005-12-06 23:45                 ` Jeff Garzik
2005-12-07 13:34                 ` Michael Buesch
2005-12-08 11:32                   ` Jiri Benc
2005-12-08 12:07           ` Jiri Benc
2005-12-08 12:12             ` Arjan van de Ven
2005-12-08 13:03               ` Jiri Benc
2005-12-05 19:10         ` Christoph Hellwig
2005-12-05 19:31           ` Jiri Benc
2005-12-05 19:41             ` Christoph Hellwig
2005-12-05 20:11               ` Jiri Benc
2005-12-06 15:09                 ` Pavel Machek
2005-12-06 16:43                   ` Ben Greear
2005-12-06 23:25                     ` David S. Miller
2005-12-06 19:24                   ` Jeff Garzik
2005-12-06 15:04             ` Pavel Machek
2005-12-08  0:00             ` Michael Wu
2005-12-08  1:05               ` Jeff Garzik
2005-12-05 20:23     ` Michael Buesch
2005-12-05 20:42       ` Jiri Benc
2005-12-06  9:26         ` Kyle Moffett
2005-12-06 10:23           ` Luc Saillard [this message]
2005-12-06 22:47 Jean Tourrilhes
2005-12-07  7:11 ` Jouni Malinen
2005-12-07 19:16   ` Jean Tourrilhes
2005-12-07 19:47     ` Jouni Malinen
2005-12-07 19:05 ` Jean Tourrilhes

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=20051206102340.GC24486@sd291.sivit.org \
    --to=luc@saillard.org \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=jbenc@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    --cc=mrmacman_g4@mac.com \
    --cc=netdev@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).