All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Gorski <jonas.gorski@gmail.com>
To: Matt Redfearn <matt.redfearn@mips.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org,
	"MIPS Mailing List" <linux-mips@linux-mips.org>,
	"James Hogan" <jhogan@kernel.org>
Subject: Re: [PATCH v2] bcma: Prevent build of PCI host features in module
Date: Sat, 10 Mar 2018 12:35:37 +0100	[thread overview]
Message-ID: <CAOiHx=n7R35yfPZgGt9pq39y-jMYpH44eAGGSvNJ=sM5Rf5H3A@mail.gmail.com> (raw)
In-Reply-To: <7a1695c0-45cf-e3d6-8524-8d2aeccc6490@mips.com>

Hi,

On 8 March 2018 at 13:00, Matt Redfearn <matt.redfearn@mips.com> wrote:
> Hi,
>
>
> On 02/03/18 17:56, Larry Finger wrote:
>>
>> On 03/01/2018 04:45 AM, Kalle Valo wrote:
>>>
>>> Matt Redfearn <matt.redfearn@mips.com> writes:
>>>
>>>> Attempting to build bcma.ko with BCMA_DRIVER_PCI_HOSTMODE=y results in
>>>> a build error due to use of symbols not exported from vmlinux:
>>>>
>>>> ERROR: "pcibios_enable_device" [drivers/bcma/bcma.ko] undefined!
>>>> ERROR: "register_pci_controller" [drivers/bcma/bcma.ko] undefined!
>>>> make[1]: *** [scripts/Makefile.modpost:92: __modpost] Error 1
>>>>
>>>> To prevent this, don't allow the host mode feature to be built if
>>>> CONFIG_BCMA=m
>>>>
>>>> Signed-off-by: Matt Redfearn <matt.redfearn@mips.com>
>>>>
>>>> ---
>>>>
>>>> Changes in v2:
>>>> Rebase on v4.16-rc1
>>>>
>>>>   drivers/bcma/Kconfig | 2 +-
>>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/bcma/Kconfig b/drivers/bcma/Kconfig
>>>> index ba8acca036df..cb0f1aad20b7 100644
>>>> --- a/drivers/bcma/Kconfig
>>>> +++ b/drivers/bcma/Kconfig
>>>> @@ -55,7 +55,7 @@ config BCMA_DRIVER_PCI
>>>>   config BCMA_DRIVER_PCI_HOSTMODE
>>>>       bool "Driver for PCI core working in hostmode"
>>>> -    depends on MIPS && BCMA_DRIVER_PCI && PCI_DRIVERS_LEGACY
>>>> +    depends on MIPS && BCMA_DRIVER_PCI && PCI_DRIVERS_LEGACY && BCMA =
>>>> y
>>>
>>>
>>> Due to the recent regression in bcma I would prefer extra careful review
>>> before I apply this. So does this look ok to everyone?
>>
>>
>> I have a preference for wireless device drivers to be modules. For that
>> reason, I would have submitted a patch exporting those two missing globals
>> rather than forcing bcma to be built in. That said, it seems that the patch
>> will do no further harm.
>
>
>
> This patch was purely intended to fix the build breakage caused by
> attempting to build host-mode PCI into a module, which fails due to
> necessary symbols not being exported by the kernel for use by modules.
>
> Making it possible to build the driver including host mode may not be as
> trivial as "lets just export the symbols", and testing that it works
> correctly once it can be built as a module will require hardware with this
> device present (which I don't have).
>
> So I would propose that this patch be merged as is, since as you say, it
> does no further harm - it should just fix build breakage - and if the
> driver, including this host mode feature, is really required as a module,
> perhaps someone with access to the hardware could spin a patch to implement
> that.


These aren't the actual wireless drivers, just the bus drivers. The
actual wireless drivers (b43 / brcmsmac) can still be built as a
module.

Also those systems that use/need the pci host driver of ssb/bcma
actually need ssb/bcma built-in anyway, as it also provides serial
console, interrupt routing, flash access, and other early init stuff.
At best one could rewrite the pci host core driver as a standalone
bcma driver, and then one could allow it to be built as a module. But
I'm not sure if it's worth it.


Regards
Jonas

  reply	other threads:[~2018-03-10 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  9:58 [PATCH v2] bcma: Prevent build of PCI host features in module Matt Redfearn
2018-03-01  9:58 ` Matt Redfearn
2018-03-01 10:45 ` Kalle Valo
2018-03-01 10:45   ` Kalle Valo
2018-03-02 17:56   ` Larry Finger
2018-03-08 12:00     ` Matt Redfearn
2018-03-08 12:00       ` Matt Redfearn
2018-03-10 11:35       ` Jonas Gorski [this message]
2018-03-13 16:48 ` [v2] " Kalle Valo
2018-03-13 16:48   ` Kalle Valo
2018-03-13 16:48 ` Kalle Valo

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='CAOiHx=n7R35yfPZgGt9pq39y-jMYpH44eAGGSvNJ=sM5Rf5H3A@mail.gmail.com' \
    --to=jonas.gorski@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jhogan@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matt.redfearn@mips.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.