From: Pavel Roskin <proski@gnu.org>
To: Alex Davis <alex14641@yahoo.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Kernel bug in bcm43xx-d80211
Date: Mon, 19 Feb 2007 19:24:03 -0500 [thread overview]
Message-ID: <1171931043.8133.4.camel@dv> (raw)
In-Reply-To: <508755.46267.qm@web50206.mail.yahoo.com>
On Mon, 2007-02-19 at 15:48 -0800, Alex Davis wrote:
> --- Pavel Roskin <proski@gnu.org> wrote:
>
> > On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> >
> > Wireless topics moved from this list to linux-wireless@vger.kernel.org.
> > Broadcom drivers are discussed in bcm43xx-dev@lists.berlios.de.
> > wireless-dev is horribly broken, and the fixes haven't been merged yet.
> >
> > The current Broadcom driver can be loaded from
> > http://bu3sch.de/git/wireless-dev.git (please load it on top of
> > wireless-dev.git to save bandwidth)
> What command do I use to load Mike's tree on top of wireless-dev?
This should do it for you:
git-remote add bcm43xx http://bu3sch.de/git/wireless-dev.git
git-branch bcm43xx
git-config branch.bcm43xx.remote bcm43xx
git-config branch.bcm43xx.merge refs/heads/master
git-checkout bcm43xx
git-pull
Sorry, I didn't expect it to be so hairy. Perhaps it should be
documented somewhere.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-20 0:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:48 Kernel bug in bcm43xx-d80211 Alex Davis
2007-02-19 22:12 ` Johannes Berg
2007-02-19 22:30 ` Pavel Roskin
2007-02-19 22:30 ` Pavel Roskin
2007-02-19 22:36 ` Johannes Berg
2007-02-19 22:21 ` Pavel Roskin
2007-02-19 23:48 ` Alex Davis
2007-02-20 0:08 ` Johannes Berg
2007-02-20 0:14 ` Johannes Berg
2007-02-20 0:23 ` Jiri Benc
2007-02-20 0:16 ` Larry Finger
2007-02-20 0:24 ` Pavel Roskin [this message]
2007-02-20 0:40 ` Alex Davis
2007-02-20 0:48 ` Pavel Roskin
2007-02-20 0:51 ` Jiri Benc
2007-02-20 3:04 ` Alex Davis
2007-02-20 3:54 ` Pavel Roskin
2007-02-20 8:25 ` Johannes Berg
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=1171931043.8133.4.camel@dv \
--to=proski@gnu.org \
--cc=alex14641@yahoo.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 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.