linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Anders <dave123_aml@yahoo.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>,
	libertas-dev@lists.infradead.org
Cc: "Harvey, Timothy" <tharvey@irobot.com>,
	feng.tang@intel.com, linux-wireless@vger.kernel.org,
	claud_yu <claud_yu@yahoo.com.tw>
Subject: Re: Alternative Libertas SDIO driver seen
Date: Mon, 14 Apr 2008 06:39:37 -0700 (PDT)	[thread overview]
Message-ID: <916547.28931.qm@web54407.mail.yahoo.com> (raw)
In-Reply-To: <200804141211.43539.hs4233@mail.mn-solutions.de>

Holger,

the moblin libertas driver is originally based on source marvell released for both the OLPC and
the UMPC, which is then used in conjunction with the atheros sdio stack that was announced some
time back:

http://www.linuxdevices.com/news/NS6177996610.html

thanks
Dave Anders


--- Holger Schurig <hs4233@mail.mn-solutions.de> wrote:

> On Monday 14 April 2008 11:12:38 claud_yu wrote:
> > Hi ,
> >
> > Currently I use wi2wi W2SW0001, I send Murata module
> > back. I still try to port the libertas driver to mx31.
> > Wi2Wi provide a SD card development card on wi2wi
> > website. I also try another 88w8686 driver from
> > project moblin (http://www.moblin.org/). The driver
> > should based on marvell SDIO driver. But the driver
> > still have some problem while firmware download.
> 
> Okay, I find a kernel tree there which, in 
> debian/patches/0019-marvell_8686_8688.patch contains another 
> libertas driver.
> 
> Unfortunately, the (Intel created) moblin.org webpage only 
> supports the "http://" access protocol to the git tree, which is 
> rather inefficent. I'm currently trying to get this tree 
> with "git clone --reference /usr/src/linux-git 
> http://www.moblin.org/repos/projects/kernel-mid-2.6.24.git/", 
> and takes ages. Maybe they also made this tree from scratch, so 
> that the reference to Linus' git tree won't help the 
> downloading.
> 
> 
> 
> Okay, to the driver:
> 
> * it's GPL, so we can copy from it
> * it's an if_sdio.c only-driver (and also contains something
>    with bluetooth stuff)
> * it's weird, as this patch contains two wlan_11.c files
>   which differ. This is true for effectively every wlan_XXX.c
>   file.
> * it looks similar to what Marvell donated originally to OLPC
> * compared to the current in-kernel libertas driver, it has
>   some more code for 802.11a frequencies
> * older Marvell drivers contained firmware as *.h files, this
>   driver now uses #include <linux/firmware.h> as well
> 
> As this driver is sdio-only, and we have already other libertas 
> drivers supported in the kernel, it would never accepted as-is 
> in mainland kernel. Therefore I invite Marvell and Intel to 
> participate with the in-kernel libertas driver. I understand 
> that for Intel this might not be possible immediately, because 
> the current libertas driver might not work on their 
> Atom-reference platform, but I guess in the long-run could be 
> beneficial.
> 
> I CC'ed feng tang from "git log 
> debian/patches/0019-marvell_8686_8688.patch" therefore :-)
> 
> _______________________________________________
> libertas-dev mailing list
> libertas-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libertas-dev
> 



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

  reply	other threads:[~2008-04-14 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <252063.3227.qm@web72209.mail.tp2.yahoo.com>
2008-04-14 10:11 ` Alternative Libertas SDIO driver seen Holger Schurig
2008-04-14 13:39   ` David Anders [this message]
2008-04-14 16:31     ` Holger Schurig
2008-04-14 17:12       ` Dan Williams
2008-04-14 15:19   ` Dan Williams
2008-04-15  2:05     ` Tang, Feng

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=916547.28931.qm@web54407.mail.yahoo.com \
    --to=dave123_aml@yahoo.com \
    --cc=claud_yu@yahoo.com.tw \
    --cc=feng.tang@intel.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tharvey@irobot.com \
    /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).