All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Michael Buesch <mbuesch@freenet.de>
Cc: bcm43xx-dev@lists.berlios.de, linux-kernel@vger.kernel.org,
	Feyd <feyd@seznam.cz>
Subject: Re: [Bcm43xx-dev] Broadcom 43xx first results
Date: Mon, 5 Dec 2005 06:41:41 -0800	[thread overview]
Message-ID: <20051205144141.GD8940@jm.kir.nu> (raw)
In-Reply-To: <200512051528.33146.mbuesch@freenet.de>

On Mon, Dec 05, 2005 at 03:28:32PM +0100, Michael Buesch wrote:

> Well, I do not care for drivers ignoring SoftMAC and duplicating
> the work. The question is: Why don't these drivers use SoftMAC?
> (Yeah, because it is incomplete, is the answer. :D I am talking
> about future.)

For me, the answer would have been because I had no idea about that
being worked on somewhere else. Now the answer would be more likely
"because it is not in netdev-2.6 tree with rest of ieee80211
development".

> What is so hard about a driver including ieee80211.h _and_
> ieee80211softmac.h, if it requires Software MAC? And what
> exactly is duplicated work here? SoftMAC does _not_ duplicate;
> it extends.

That is not hard as long as this work is easily available.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2005-12-05 14:42 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04 18:50 Broadcom 43xx first results mbuesch
2005-12-04 19:52 ` [Bcm43xx-dev] " Feyd
2005-12-04 19:58   ` Michael Buesch
2005-12-05  5:50     ` Jouni Malinen
2005-12-05  6:05       ` Benjamin Herrenschmidt
2005-12-05 11:08       ` Michael Buesch
2005-12-05 14:19         ` Jouni Malinen
2005-12-05 14:28           ` Michael Buesch
2005-12-05 14:41             ` Jouni Malinen [this message]
2005-12-05 18:52             ` Jeff Garzik
2005-12-05 19:20               ` Christoph Hellwig
2005-12-05 18:00 ` Jiri Benc
2005-12-05 18:14   ` Michael Renzmann
2005-12-05 18:24     ` Stephen Hemminger
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-30 10:34             ` Rakotomandimby Mihamina
2005-12-06  7:17       ` Michael Renzmann
2005-12-05 18:38   ` Joseph Jezak
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-06 20:53               ` Stephen Hemminger
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:23     ` Michael Buesch
2005-12-05 20:42     ` Jiri Benc
2005-12-06  9:26       ` Kyle Moffett
2005-12-06 10:23         ` Luc Saillard
2005-12-05 19:40 ` Pavel Machek
2005-12-05 20:14   ` Michael Buesch
2005-12-05 20:35     ` Pavel Machek
2005-12-05 20:40       ` Arjan van de Ven
2005-12-05 20:40       ` Michael Buesch

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=20051205144141.GD8940@jm.kir.nu \
    --to=jkmaline@cc.hut.fi \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=feyd@seznam.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.