From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: bcm43xx-dev@lists.berlios.de,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Current linus git bcm4xxx broken for me
Date: Sat, 15 Apr 2006 21:27:11 +0200 [thread overview]
Message-ID: <1145129231.6560.4.camel@localhost> (raw)
In-Reply-To: <1144974919.4686.1.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On Fri, 2006-04-14 at 10:35 +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2006-04-14 at 10:02 +1000, Benjamin Herrenschmidt wrote:
> > I get that with current upstream git :
>
> .../...
>
> Correction: It actually works after tickling softmac a bit (it's an open
> network with non advertised essid, the init scripts are supposedly
> setting the essid but softmac is having some vapors, changing the essid
> manually a couple of times and it ends up associating).
Below ...
> Still, the dmesg filling up with those messages is pretty nasty :)
There are two issues here. One is the messages (related to it being a
0x4318) and secondly that softmac isn't behaving will :)
I'm trying to fix the latter but can't really pinpoint the problem yet.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-04-15 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 0:02 Current linus git bcm4xxx broken for me Benjamin Herrenschmidt
2006-04-14 0:35 ` Benjamin Herrenschmidt
2006-04-15 19:27 ` Johannes Berg [this message]
2006-04-14 11:43 ` Michael Buesch
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=1145129231.6560.4.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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.