Ronald G Minnich <[EMAIL PROTECTED]> writes:
> On Wed, 4 Jul 2001, Armin Schindler wrote:
>
> > Maybe there already is, but what I didn't find yet are some
> > "hooks" in the code at specific locations, where the user/customer
> > can include their own additional init code without changing the main
> > files.
>
> This is a common problem we've seen with the embedded guys, and I don't
> think we've got it right yet. We can try to help make this a better job if
> you can tell us what we need to od.
Ron I will totally agree with this. The current structure works, but only
very roughly. On my todo list is to figure out how we can do dependency
driver device enumeration/configuration.
On a system with a host bridge <-> PCI bus setup.
(hardcode enumerate the host bridge)
init host bridge
enumerate pci bus
(init pci<->pci bridges)
enumerate sub pci buses, repeat
(init pci<->isa bridges)
enumerate isa devices
(finally initialize all devices on pci bridge)
In practice we need a step that allocates resources seperately from
initializing the devices.
This doesn't provide everything but it should handle all of the common
cases. And after that is figured out main should be clean enough that
we can actually figure out what additional hooks make sense to add.
Eric
