Linux wireless drivers development
 help / color / mirror / Atom feed
From: Taketo Kabe <kabe@sra-tohoku.co.jp>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: prabhu <d.praabhu@gmail.com>,
	kvalo@codeaurora.org, m@bues.ch, linux-wireless@vger.kernel.org,
	b43-dev@lists.infradead.org, kabe@sra-tohoku.co.jp
Subject: Re: [Regression]BCM4312 is broken in kernel 4.18[Root cause found]
Date: Tue, 28 Aug 2018 21:41:19 +0900	[thread overview]
Message-ID: <5B8542EF.6040405@sra-tohoku.co.jp> (raw)
In-Reply-To: <25814b23-dcc9-3a20-7276-40818bbba6cb@lwfinger.net>

> @Pradhu & @Taketo: Attached is a new (improved?) patch for you to try. You need 
> to start from an unmodified 4.18 source. This patch should allow both of your 
> systems to work and avoid needing to revert Taketo's fix for his setup.
> 
> Thanks,
> Larry

Sorry for tha late reply.
Tested out the patch on clean 4.18.5 kernel source; it works as expected.

I also tried out proprietary firmware, but I couldn't reproduce a problem
mentioned in https://marc.info/?l=linux-wireless&m=153504546924558&w=2 .
The proprietary firmware works very sluggishly on my card (BCM4306)
and doesn't stand for practical use for unknown reason.
-- 
kabe

  parent reply	other threads:[~2018-08-28 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 17:30 [Regression]BCM4312 is broken in kernel 4.18[Root cause found] prabhu
2018-08-23 18:11 ` Michael Büsch
2018-08-24  8:23   ` Kalle Valo
2018-08-24 16:15     ` Larry Finger
2018-08-26  7:23       ` prabhu
2018-08-26 16:14         ` Larry Finger
2018-08-27 11:30           ` prabhu
2018-08-27 15:28             ` Larry Finger
     [not found]               ` <CAHnrWRpPzV5BK3BoMrQ1vH=nxu70dVONLdhCnHh0SpBEa2v5LQ@mail.gmail.com>
2018-09-04 15:15                 ` Larry Finger
2018-08-28 12:41           ` Taketo Kabe [this message]
2018-08-23 19:20 ` Larry Finger
2018-08-24  7:54   ` prabhu

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=5B8542EF.6040405@sra-tohoku.co.jp \
    --to=kabe@sra-tohoku.co.jp \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=d.praabhu@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m@bues.ch \
    /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