linux-mips
[Top] [All Lists]

Re: [PATCH 4/7] MIPS: ath79: add a common PCI registration function

To: René Bolldorf <xsecute@googlemail.com>
Subject: Re: [PATCH 4/7] MIPS: ath79: add a common PCI registration function
From: Gabor Juhos <juhosg@openwrt.org>
Date: Fri, 18 Nov 2011 19:41:39 +0100
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
In-reply-to: <CAEWqx59XzDyGWi7q-PYjiXx7t1Jinoz8ygypbk65CmD+zcyW2g@mail.gmail.com>
References: <1321629720-29035-1-git-send-email-juhosg@openwrt.org> <1321629720-29035-4-git-send-email-juhosg@openwrt.org> <CAEWqx59XzDyGWi7q-PYjiXx7t1Jinoz8ygypbk65CmD+zcyW2g@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
2011.11.18. 19:32 keltezéssel, René Bolldorf írta:
> On Fri, Nov 18, 2011 at 4:21 PM, Gabor Juhos <juhosg@openwrt.org> wrote:
>> The current code unconditionally registers the AR724X
>> specific PCI controller, even if the kernel is running
>> on a different SoC.
>>
> This is not true, take a look in the ath79 Kconfig file...

Well, it is true. If you have the Ubiquiti board selected, that will allow you
to select the PCI code to be built. If you select the PCI code as well, then
pci-ath724x.c will be compiled into the kernel. Due to the nature of the
'arch_initcall' macro the PCI controller always gets registered. If you have
another board selected along with the Ubiquiti, and you are trying to run the
kernel on the other board, the PCI controller will be registered on that as 
well.

-Gabor

<Prev in Thread] Current Thread [Next in Thread>