public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Chris Vine <vine35792468@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Regression: bcm4312 lp-phy device not working in 4.17-rc5 kernel
Date: Mon, 14 May 2018 20:02:05 +0200	[thread overview]
Message-ID: <20180514200205.47814f60@wiggum> (raw)
In-Reply-To: <20180514195539.74686870@wiggum>

On Mon, 14 May 2018 19:55:39 +0200
Michael B?sch <m@bues.ch> wrote:

> On Mon, 14 May 2018 18:49:53 +0100
> Chris Vine <vine35792468@gmail.com> wrote:
> 
> > I have an old netbook with a Broadcom bcm4312 802.11b/g lp-phy
> > [14e4:4315] (rev 01) wifi device.  This works up to and including the
> > 4.16 kernel, but not with 4.17-rc5.
> > 
> > The b43, mac80211, cfg80211, ssb and mmc_core modules are loaded OK, as
> > is the firmware, and the wlan0 interface will come up, but any attempt
> > to use the interface fails and it cannot (for example) scan.
> > 
> > No useful error messages are given.  The interface (wlan0) is just
> > reported as not being ready.  
> 
> Hi,
> 
> thanks for your report.
> 
> Can you please provide all kernel log messages anyway?
> And what does "not ready" mean exactly?
> 
> It would be extremely helpful if you'd do a git bisect to find the
> commit that broke it.
> 

Ok, I just noticed that mainline still contains the ssb breakage.

So you are most likely hitting this:
https://patchwork.kernel.org/patch/10393729/


-- 
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20180514/7e1e9beb/attachment.sig>

  reply	other threads:[~2018-05-14 18:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 17:49 Regression: bcm4312 lp-phy device not working in 4.17-rc5 kernel Chris Vine
2018-05-14 17:55 ` Michael Büsch
2018-05-14 18:02   ` Michael Büsch [this message]
2018-05-14 18:37     ` 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=20180514200205.47814f60@wiggum \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vine35792468@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