Re: OFWBUS: How does autoconfiguration work?

I am working on an operating systems project at my university, which
currently
uses lazy driver initialization i.e. that is the drivers initialize the
hardware only
during the first invocation, for example, the UART hardware is initialized
only during the first call to output_char.

Currently, we have multiple BSP's to support different variants even though
they are quite similar. For example, we have two BSPs to support BeagleBone
Black
and white. We are trying to avoid this by using device tree files. Our goal
is to parse the
DTB at boot time and call all the registered drivers to initialize the
hardware. By registered
drivers, I mean drivers which are statically linked to executable.

I am trying to add a system, which will parse the DTB files and initialize
them by calling
the appropriate drivers. I want a system similar to FreeBSD or Linux
a probe and attach method for device drivers. It doesn't have to be as
complex as FreeBSD
but a simple one will do.

If you have any other questions please let me know :)

Thanks,
Niteesh

On Sun, Feb 2, 2020 at 9:07 PM Ian Lepore <ian_at_freebsd.org> wrote:

> On Sun, 2020-02-02 at 10:02 +0530, Niteesh wrote:
> > I couldn't find anything useful for me, I need information about how the
> > hardware autoconfiguration works, not autoconf.
> >
>
> Then maybe you need to provide more details about what you're doing,
> what you've tried that isn't working, or something.  I couldn't make
> any sense out of your original question.
>
> -- Ian
>
>