On Wednesday 03 September 2014 21:18:12 Xia Kaixu wrote:
>
> +#ifdef CONFIG_PCI
> +extern int __init cns3xxx_pcie_init_late(void);
> +#else
> +static inline int __init cns3xxx_pcie_init_late(void)
> +{
> + return -ENXIO;
> +}
> +#endif
> +
> void __init cns3xxx_map_io(void);
>
I found ano
On Wednesday 03 September 2014, Xia Kaixu wrote:
> From: Xia Kaixu
>
> The kernel panic occurs when running an allmodconfig kernel on
> OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
> hardware it's running on and just tries to access to its specific
> registers. Now call it fro
δΊ 2014/9/3 21:27, Arnd Bergmann ει:
> On Wednesday 03 September 2014 21:18:12 Xia Kaixu wrote:
>> From: Xia Kaixu
>>
>> The kernel panic occurs when running an allmodconfig kernel on
>> OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
>> hardware it's running on and just tries to ac
On Wednesday 03 September 2014 21:18:12 Xia Kaixu wrote:
> From: Xia Kaixu
>
> The kernel panic occurs when running an allmodconfig kernel on
> OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
> hardware it's running on and just tries to access to its specific
> registers. Now cal
From: Xia Kaixu
The kernel panic occurs when running an allmodconfig kernel on
OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
hardware it's running on and just tries to access to its specific
registers. Now call it from .init_late callback from the two
machine descriptors.
Sign
From: Xia Kaixu
The kernel panic occurs when running an allmodconfig kernel on
OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
hardware it's running on and just tries to access to its specific
registers. Now call it from .init_late callback from the two
machine descriptors.
Sign
6 matches
Mail list logo
