From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ch1ehsobe005.messaging.microsoft.com ([216.32.181.185]:9368 "EHLO ch1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758312Ab2EOI7d (ORCPT ); Tue, 15 May 2012 04:59:33 -0400 Message-ID: <4FB21AE3.80301@netgem.com> (sfid-20120515_105938_141322_9988967F) Date: Tue, 15 May 2012 10:59:15 +0200 From: "F. LECAILLE" MIME-Version: 1.0 To: Arend van Spriel CC: Subject: Re: broadcom 43236B USB module References: <4FB2033B.4070701@netgem.com> <4FB21985.9090306@broadcom.com> In-Reply-To: <4FB21985.9090306@broadcom.com> Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On 05/15/12 10:53, Arend van Spriel wrote: > On 05/15/2012 09:18 AM, F. LECAILLE wrote: >> Hello, >> >> I have some Wifi USB modules with 43236B Broadcom chipset. I have read on the >> linuxwireless dot org website that this chipset is supported by the brcmfmac >> *(USB)* driver. >> >> As I am also trying to backport this driver for an embedded device which runs a >> 2.6.27 kernel, I had a look to the 3.2 kernel sources and especially to the >> drivers/net/wireless/brcm80211/brcmfmac directory. But I do not find any >> reference to USB stack kernel functions. >> >> How may this work? > > It works by being patient. USB support was merged upstream in the > previous merge window so it is present in the current 3.4-rcX releases. > If you want to backport I suggest to use compat-wireless (see [1]) as it > does a lot of work for you. > > Gr. AvS > > [1] http://linuxwireless.org/en/users/Download > > > Ok. I understand. Thank you Arend.