Subject: Re: [Bcm43xx-dev] Broadcom 43xx first results
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: Michael Buesch <mbuesch@freenet.de>, Feyd <feyd@seznam.cz>,
       linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de
In-Reply-To: <20051205055012.GE8953@jm.kir.nu>
References: <E1Eiyw4-0003Ab-FW@www1.emo.freenet-rz.de>
	 <20051204205208.46e44480@epsilon.site>
	 <200512042058.30801.mbuesch@freenet.de>  <20051205055012.GE8953@jm.kir.nu>
Content-Type: text/plain
Date: Mon, 05 Dec 2005 17:05:34 +1100
Message-Id: <1133762735.6100.137.camel@gaston>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1002
Lines: 22


> Wouldn't it be better to try to get that functionality added into the
> net/ieee80211 code instead of maintaining separate extension outside the
> kernel tree? Many modern cards need the ability for the host CPU to take
> care of management frame sending and receiving and from my view point,
> this code should be in net/ieee80211. Many (all?) of the functions in
> this "SoftMAC" look like something that would be nice to have as an
> option in net/ieee80211. In other words, the low-level driver would
> indicate what kind of functionality it needs and ieee80211 stack would
> behave differently based on the underlying hardware profile.

It would certainly be a good idea and I'm sure that's what will happen
once the code is mature enough ;)

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/