Date: Tue, 4 Feb 2020 19:09:36 +0530 From: Niteesh <gsnb.gn@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: OFWBUS: How does autoconfiguration work? Message-ID: <CAD=CwDHrpNJb3B=miVgNOFx8iS1tD=4G7fFz%2Bp7La3jNkMoH8Q@mail.gmail.com> In-Reply-To: <e67943522274228c79ada6b03b1ee6ac08b897c2.camel@freebsd.org> References: <CAD=CwDGyr49%2BL26ODY5V1g6=6CrB9cw64dDFpdq6xhxJS7hdiA@mail.gmail.com> <CAGLDxTUeuaW0wm6Y24fm41NB40CNshf_35N4LBiQXQJ1%2Bhbppw@mail.gmail.com> <CAD=CwDFZdwcQe5Lpks5Ki7A=6yiuKGEMpKX4KzkSYF-e9qQ8jg@mail.gmail.com> <e67943522274228c79ada6b03b1ee6ac08b897c2.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD=CwDHrpNJb3B=miVgNOFx8iS1tD=4G7fFz%2Bp7La3jNkMoH8Q>