From: "Michael Büsch" <m@bues.ch>
To: Wirz <spam@lukas-wirz.de>
Cc: b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: b43 crashes on rmmod (bcm4331)
Date: Wed, 13 Jun 2018 13:09:05 +0200 [thread overview]
Message-ID: <20180613130905.420695e7@wiggum> (raw)
In-Reply-To: <538cd7b7-8d63-1795-7bfc-69231d2bf3c0@lukas-wirz.de>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On Wed, 13 Jun 2018 14:01:53 +0300
Wirz <spam@lukas-wirz.de> wrote:
> > CONFIG_B43_HWRNG completely switches off hwrng support in b43.
> > I don't see how a change in hwrng core could still lead to a crash in
> > b43 with this option switched off.
> >
> > What do you mean by "manually in the .config"?
>
> What I meant is, that I have outcommented the line 'CONFIG_B43_HWRNG=y'
> in .config.
>
> > Can you try to properly switch off the setting with make menuconfig and
> > then recompile everything from scratch (make clean)?
>
> I was intending to do that before, but I cannot find the option for
> that. Searching for b43_hwrng in menuconfig only shows the dependencies
> of that option, and the Kconfig file where it is defined, but not the
> path in menuconfig. Do I indirectly set CONFIG_B43_HWRNG through the
> parameters it depends on? I'm sorry, but this is obviously above my
> level of expertise ...
Whoops, sorry. You are right. This is an automatic config option.
That also means your manual editing of .config would be overridden.
You can edit drivers/net/wireless/broadcom/b43/Kconfig
go to the section config B43_HWRNG
and change 'default y' to 'default n'
That should disable it.
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-13 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 19:55 b43 crashes on rmmod (bcm4331) Wirz
2018-06-09 12:08 ` Wirz
2018-06-09 15:11 ` Michael Büsch
2018-06-09 19:46 ` Wirz
2018-06-09 20:01 ` Michael Büsch
2018-06-11 20:09 ` Wirz
2018-06-11 20:46 ` Michael Büsch
2018-06-13 9:25 ` Wirz
2018-06-13 10:27 ` Michael Büsch
2018-06-13 11:01 ` Wirz
2018-06-13 11:09 ` Michael Büsch [this message]
2018-06-13 12:01 ` Michael Büsch
2018-06-13 13:07 ` Wirz
2018-06-13 13:28 ` Michael Büsch
2018-06-14 9:47 ` Wirz
2018-06-14 16:26 ` Michael Büsch
2018-06-14 19:18 ` Wirz
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=20180613130905.420695e7@wiggum \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=spam@lukas-wirz.de \
/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).