linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Franz Apeltauer <franz.apeltauer@gmx.at>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 2 compile errors: rt2x00firmware.c and mesh.c
Date: Thu, 06 Mar 2008 00:12:50 +0100	[thread overview]
Message-ID: <47CF28F2.6050509@gmx.at> (raw)
In-Reply-To: <20080303035222.GP28995@ruslug.rutgers.edu>

Luis R. Rodriguez schrieb:
> Forced a new tarball out with new changes applied, would appreciate
> some testing on 2.6.21, 2.6.22. You can get the tarball from the
> usual place:
> http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2

Thank you very much!
Now everything compiles fine on 2.6.22.

I cannot send you test results yet. It looks like I have to read some 
more documentation first. For now I can only tell you this:

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.
# modprobe b43legacy
=> messages: Mar  5 23:14:02 af-nb-3 kernel: [10519.728000] Broadcom 
43xx driver loaded [ Features: PID, Firmware-ID: FW10 ]
=> dmesg: [10519.728000] Broadcom 43xx driver loaded [ Features: PID, 
Firmware-ID: FW10 ]

Maybe this is important: dmesg says "Firmware-ID: FW10", but there is no 
ucode10.fw in /lib/firmware/b43legacy, only 2, 4, 5, 11 (downloaded 
today, as described in the wiki).

# lsmod | grep 43
b43legacy             102040  0
ssb                    36484  1 b43legacy
mac80211              220020  1 b43legacy

# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset 
Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g 
Wireless LAN Controller (rev 03)
...


b) Test on a PC with MSI PC54G2 ... RaLink rt2500
You wrote "For now I'll disable rt2x00 in compat-wireless."
So, the result of this test seems to be unimportant (it tried to load 
the old driver).


If you would like to see the output of any test, that I can do for you, 
just let me know.

Greetings,
Franz

  reply	other threads:[~2008-03-05 23:13 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 [this message]
2008-03-05 23:15       ` Johannes Berg
2008-03-05 23:25         ` Franz Apeltauer
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=47CF28F2.6050509@gmx.at \
    --to=franz.apeltauer@gmx.at \
    --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 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).