From: Matt Redfearn <matt.redfearn@mips.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Michael Büsch" <m@bues.ch>, "Rafał Miłecki" <zajec5@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression caused by commit 882164a4a928
Date: Wed, 9 May 2018 13:55:43 +0100 [thread overview]
Message-ID: <372d149c-c34c-56a0-4e1a-5ab2c1e16e73@mips.com> (raw)
In-Reply-To: <7bbc067a-c412-3d2e-174a-abc31b46e246@lwfinger.net>
Hi Larry
On 07/05/18 16:44, Larry Finger wrote:
> Matt,
>
> Although commit 882164a4a928 ("ssb: Prevent build of PCI host features
> in module") appeared to be harmless, it leads to complete failure of
> drivers b43. and b43legacy, and likely affects b44 as well. The problem
> is that CONFIG_SSB_PCIHOST is undefined, which prevents the compilation
> of the code that controls the PCI cores of the device. See
> https://bugzilla.redhat.com/show_bug.cgi?id=1572349 for details.
Sorry for the breakage :-/
>
> As the underlying errors ("pcibios_enable_device" undefined, and
> "register_pci_controller" undefined) do not appear on the architectures
> that I have tested (x86_64, x86, and ppc), I suspect something in the
> arch-specific code for your setup (MIPS?). As I have no idea on how to
> fix that problem, would the following patch work for you?
>
> diff --git a/drivers/ssb/Kconfig b/drivers/ssb/Kconfig
> index 9371651d8017..3743533c8057 100644
> --- a/drivers/ssb/Kconfig
> +++ b/drivers/ssb/Kconfig
> @@ -117,7 +117,7 @@ config SSB_SERIAL
>
> config SSB_DRIVER_PCICORE_POSSIBLE
> bool
> - depends on SSB_PCIHOST && SSB = y
> + depends on SSB_PCIHOST && (SSB = y || !MIPS)
> default y
>
> config SSB_DRIVER_PCICORE
I believe that the problem stems from these drivers being used for some
wireless AP functionality built into some MIPS based SoCs. The Kconfig
rules sort out building this additional functionality when configured
for MIPS (in a round about sort of way), but it allowed it even when SSB
is a module, leading to build failures. My patch was intended to prevent
that.
There was a similar issue in the same Kconfig file, introduced by
c5611df96804 and fixed by a9e6d44ddecc. It was fixed the same way as you
suggest. I've tested the above patch and it does work for MIPS
(preventing the PCICORE being built into the module).
Tested-by: Matt Redfearn <matt.redfearn@mips.com>
Thanks & sorry again for the breakage,
Matt
>
> Thanks,
>
> Larry
next prev parent reply other threads:[~2018-05-09 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:44 Regression caused by commit 882164a4a928 Larry Finger
2018-05-07 18:43 ` Michael Büsch
2018-05-07 19:03 ` Kalle Valo
2018-05-07 19:30 ` Michael Büsch
2018-05-09 10:03 ` Kalle Valo
2018-05-09 12:55 ` Matt Redfearn [this message]
2018-05-09 16:27 ` Michael Büsch
2018-05-10 10:24 ` Matt Redfearn
2018-05-10 11:09 ` Michael Büsch
2018-05-10 10:41 ` Rafał Miłecki
2018-05-10 10:48 ` Rafał Miłecki
2018-05-10 10:49 ` Matt Redfearn
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=372d149c-c34c-56a0-4e1a-5ab2c1e16e73@mips.com \
--to=matt.redfearn@mips.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox