From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: Andy Green <andy@warmcat.com>
Subject: Re: libertas: blows chunks on failed firmware load
Date: Wed, 1 Aug 2007 11:31:22 +0200 [thread overview]
Message-ID: <200708011131.22390.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <46B04704.3000409@warmcat.com>
> Sure I will try it tonight, where should I go to get it? The
> only trees with "libertas" in the name on git.kernel.org don't
> seem to be the ones.
My driver is for sure in the libertas-dev tree from the OLPC
people. The SVN project that contains the firmware cutter also
contains code to checkout this tree and select the proper branch
in this tree.
Basically, you do
git clone --reference XXXX git://git.infradead.org/libertas-2.6
cd libertas-2.6
git branch libertas-cf
git checkout libertas-cf
git pull origin libertas
However, I've "Signed-Up" this driver and asked Dan to forward it
into wireless-dev. He hasn't done this yet :-(
If anyone want's to review the patch (in addition to what people
did on the libertas-dev mailing list), here's an URL:
http://git.infradead.org/?p=libertas-2.6.git;a=commitdiff;h=9e25bb4c6ed9430e166b69f9f91bfccd96f0869d
next prev parent reply other threads:[~2007-08-01 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 19:45 libertas: blows chunks on failed firmware load Andy Green
2007-08-01 2:34 ` Dan Williams
2007-08-01 2:35 ` Dan Williams
2007-08-01 5:52 ` Andy Green
2007-08-01 7:00 ` Holger Schurig
2007-08-01 8:40 ` Andy Green
2007-08-01 9:31 ` Holger Schurig [this message]
2007-08-01 9:53 ` Andy Green
2007-08-01 11:01 ` Dan Williams
2007-08-01 22:31 ` Andy Green
2007-08-02 6:26 ` Holger Schurig
2007-08-02 6:40 ` Andy Green
2007-08-01 11:03 ` Dan Williams
2007-08-01 11:15 ` Holger Schurig
2007-08-01 11:35 ` Dan Williams
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=200708011131.22390.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=andy@warmcat.com \
--cc=linux-wireless@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).