From: Greg KH <greg@kroah.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
roman-vl@meta.ua, linux-wireless@vger.kernel.org
Subject: Re: b43 scans wifi networks with old firmware only.
Date: Fri, 4 Nov 2011 13:32:39 -0700 [thread overview]
Message-ID: <20111104203239.GB6833@kroah.com> (raw)
In-Reply-To: <CACna6ryKdReeSAP6W=PYBT3LnFBe-iL3daKFFxzK56TFNUW+Qw@mail.gmail.com>
On Fri, Nov 04, 2011 at 11:27:06AM +0100, Rafał Miłecki wrote:
> W dniu 4 listopada 2011 01:37 użytkownik Larry Finger
> <Larry.Finger@lwfinger.net> napisał:
> > On 11/03/2011 05:37 PM, Rafał Miłecki wrote:
> >>
> >> 2011/11/3 Larry Finger<Larry.Finger@lwfinger.net>:
> >>>
> >>> On 11/03/2011 06:21 AM, Roman V.Leon. wrote:
> >>>>
> >>>> Hello Gents.
> >>>> I have problem with b43 driver 5.100.138, it's not scanning networks for
> >>>> unknown reason. I have broadcom wifi card PCIID is 14e4:4315, linux kern
> >>>> ver. is 3.0. When i'm trying to launch iwlist scan, i'm getting "no scan
> >>>> results".
> >>>>
> >>>> for example:
> >>>> sudo ifconfig wlan0 up
> >>>> sudo iwlist wlan0 scan
> >>>> No scan results.
> >>>>
> >>>> With the older driver 5.10.56.2808, i see normal scan results. If you
> >>>> need
> >>>> any more information, i will send.
> >>>
> >>> The condition you report is known. Broadcom changed the TX/RX header
> >>> structure with firmware versions greater than 600, as shown by a 'dmesg |
> >>> grep firmware'. Those changes are not implemented in b43 until kernel
> >>> 3.2.
> >>>
> >>> These numbers are not b43 driver numbers, nor are they firmware numbers
> >>> reported by b43. They are the versions of Broadcom drivers.
> >>>
> >>> If you look at
> >>> http://wireless.kernel.org/en/users/Drivers/b43#firmwareinstallation, you
> >>> will see that firmware should be extracted from Broadcom driver 5.100.138
> >>> "if you are using kernel 3.2 or newer". For older kernels you should
> >>> extract
> >>> firmware from the 5.10.56.27.3 of the Broadcom proprietary driver. Of
> >>> course, 5.10.56.2808 will also work.
> >>>
> >>> You could also get those changes by employing a bleeding-edge version of
> >>> compat-wireless. In that case, firmware from 5.100.138 would work.
> >>
> >> Should we/can we send patch for at least 3.0.x and 3.1.x kernels
> >> adding error on loading too new firmware?
> >
> > I think adding an error would have been appropriate. We certainly cannot
> > prevent versionitis; however, getting a patch into those kernels that is not
> > in mainline might be a problem.
>
> Greg: the problem with b43 happens when kernels 3.1- users install
> firmware supported by kernels 3.2+.
Ick, that sucks.
> Is this possible to grab some separated patch for that older kernels?
> The ideal way to do this was:
> 1) Commit error enabling patch with Cc: stable
> 2) Add support for new firmwares
> 3) Drop error
> Unfortunately I didn't think about that, now it's too late.
Sure, just let me know what patch you want added to the 3.1-stable tree
and I'll add it.
thanks,
greg k-h
prev parent reply other threads:[~2011-11-04 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 11:21 b43 scans wifi networks with old firmware only Roman V.Leon.
2011-11-03 15:12 ` Larry Finger
2011-11-03 20:22 ` Roman V.Leon.
2011-11-03 22:37 ` Rafał Miłecki
2011-11-04 0:37 ` Larry Finger
2011-11-04 10:27 ` Rafał Miłecki
2011-11-04 20:32 ` Greg KH [this message]
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=20111104203239.GB6833@kroah.com \
--to=greg@kroah.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=roman-vl@meta.ua \
--cc=zajec5@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.