Can we only load the bus driver that is required by timer or pic? Then you
don't need worry about acpi_pci or pcib.
John Baldwin 于2016年4月20日周三 上午3:26写道：
> On Tuesday, April 19, 2016 03:42:40 PM Howard Su wrote:
> > On Tue, Apr 19, 2016 at 2:53 AM John Baldwin wrote:
> >
> > > On Monday, April 18
On Tuesday, April 19, 2016 03:42:40 PM Howard Su wrote:
> On Tue, Apr 19, 2016 at 2:53 AM John Baldwin wrote:
>
> > On Monday, April 18, 2016 11:10:12 PM Howard Su wrote:
> > > I noticed several places there are code like this, especially in some arm
> > > low level drivers.
> > > EARLY_DRIVER_MO
On Tue, Apr 19, 2016 at 2:53 AM John Baldwin wrote:
> On Monday, April 18, 2016 11:10:12 PM Howard Su wrote:
> > I noticed several places there are code like this, especially in some arm
> > low level drivers.
> > EARLY_DRIVER_MODULE(aw_ccu, simplebus, aw_ccu_driver, aw_ccu_devclass,
> > 0, 0
On Monday, April 18, 2016 11:10:12 PM Howard Su wrote:
> I noticed several places there are code like this, especially in some arm
> low level drivers.
> EARLY_DRIVER_MODULE(aw_ccu, simplebus, aw_ccu_driver, aw_ccu_devclass,
> 0, 0, BUS_PASS_BUS + BUS_PASS_ORDER_MIDDLE);
>
> I feel the usage
I noticed several places there are code like this, especially in some arm
low level drivers.
EARLY_DRIVER_MODULE(aw_ccu, simplebus, aw_ccu_driver, aw_ccu_devclass,
0, 0, BUS_PASS_BUS + BUS_PASS_ORDER_MIDDLE);
I feel the usage of BUS_PASS_ORDER_MIDDLE is misused. There are another
macro EARLY_
