From: Franz Apeltauer <franz.apeltauer@gmx.at>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: 2 compile errors: rt2x00firmware.c and mesh.c
Date: Thu, 06 Mar 2008 00:25:21 +0100 [thread overview]
Message-ID: <47CF2BE1.2020305@gmx.at> (raw)
In-Reply-To: <1204758941.25502.93.camel@johannes.berg>
Johannes Berg schrieb:
>> a) Test on a PC with a Broadcom 4306 rev 03:
>> - Downloaded and installed the firmware.
>> - The module b43legacy loads without errors, but nothing else happens.
>> ifconfig doesn't show any new interface, like eth0 or wlan0.
>
> Well, yeah, you need b43...
>
> johannes
I'm sorry, almost the same result:
# rmmod b43legacy
# modprobe b43
=> messages: Mar 6 00:18:36 af-nb-3 kernel: [14393.692000] Broadcom
43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
=> dmesg: [14393.692000] Broadcom 43xx driver loaded [ Features: PML,
Firmware-ID: FW13 ]
Again: No new interfaces.
Franz
next prev parent reply other threads:[~2008-03-05 23:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 23:42 2 compile errors: rt2x00firmware.c and mesh.c Franz Apeltauer
2008-03-03 0:32 ` Johannes Berg
2008-03-03 3:52 ` Luis R. Rodriguez
2008-03-05 23:12 ` Franz Apeltauer
2008-03-05 23:15 ` Johannes Berg
2008-03-05 23:25 ` Franz Apeltauer [this message]
2008-03-05 23:34 ` Johannes Berg
2008-03-10 23:09 ` Franz Apeltauer
2008-03-08 2:59 ` Luis R. Rodriguez
2008-03-10 21:41 ` Franz Apeltauer
2008-03-10 22:21 ` Ivo van Doorn
2008-03-10 23:33 ` Luis R. Rodriguez
2008-03-11 0:07 ` Franz Apeltauer
2008-03-11 1:26 ` Luis R. Rodriguez
2008-03-11 20:06 ` Hauke Mehrtens
2008-03-11 21:24 ` Luis R. Rodriguez
2008-03-11 22:14 ` Franz Apeltauer
2008-03-11 22:22 ` Ivo van Doorn
2008-03-11 23:01 ` Franz Apeltauer
2008-03-11 23:09 ` Ivo van Doorn
2008-03-16 0:33 ` Franz Apeltauer
2008-03-17 17:12 ` Luis R. Rodriguez
2008-03-03 9:37 ` Ivo Van Doorn
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=47CF2BE1.2020305@gmx.at \
--to=franz.apeltauer@gmx.at \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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 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.