public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Chris Vine <vine35792468@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Regression: bcm4312 lp-phy device not recognized in 4.15 kernel
Date: Sun, 4 Feb 2018 22:00:32 +0000	[thread overview]
Message-ID: <20180204220032.3c339324@bother.homenet> (raw)
In-Reply-To: <935a4987-c481-f4e4-16d7-f5f56adcfee0@gmail.com>

On Sun, 4 Feb 2018 12:03:49 -0800
Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 02/04/2018 10:58 AM, Chris Vine wrote:
> > I probably should have copied this to the relevant kernel wireless
> > mailing lists.  Anyway, here it is.
> > 
> > As a further datum point, the b43 driver works fine with the
> > 4.15.0-rc3 kernel.  So something seems to have changed between that
> > and 4.15.0.
> 
> Does this patch help?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=a9e6d44ddeccd3522670e641f1ed9b068e746ff7

Yes, I have wireless working again.

I'll recompile tomorrow from a fresh kernel tree and apply the patch
again and make sure it still works.  I will let you know.

-----------------------------------------
> > 
> > Begin forwarded message:
> > 
> > Date: Mon, 29 Jan 2018 23:37:49 +0000
> > From: Chris Vine <vine35792468@gmail.com>
> > To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> > Subject: Regression: bcm4312 lp-phy device not recognized in 4.15
> > kernel
> > 
> > 
> > I have an old netbook with a Broadcom bcm4312 802.11b/g lp-phy
> > [14e4:4315] (rev 01) wifi device.  It is no longer recognized in
> > kernel 4.15: it works fine with the 4.14 kernel and earlier, with
> > the b43 and ssb kernel modules.
> > 
> > I cannot give any further information as there are no error messages
> > logged. The b43 firmware (wl-5.100.138) is not loaded for it, nor
> > are the ssb/b43/bcma/ mmc_core/mac80211/cfg80211 modules.  The
> > modules can be loaded by hand without error, but nothing happens
> > and no network interface is presented.
> > 
> > This is a pretty slow and rubbish netbook but is useful when
> > travelling to a country which might impound your laptop (no names)
> > and you don't mind too much losing it.  It would be nice to
> > continue to be able to use it for that.
> > 
> > Chris
> > 

  reply	other threads:[~2018-02-04 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 18:58 Fw: Regression: bcm4312 lp-phy device not recognized in 4.15 kernel Chris Vine
2018-02-04 20:03 ` Florian Fainelli
2018-02-04 22:00   ` Chris Vine [this message]
2018-02-05 10:26     ` Chris Vine

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=20180204220032.3c339324@bother.homenet \
    --to=vine35792468@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=f.fainelli@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox