That's correct. This is actually part of a larger effort to open up the MIPS code to a range of new bootstraps. Some bootstraps use the bootinfo facility extensively. It's an easy way to pass some simple information to the kernel without the clutter of metadata and other such things.
................................... Andrew Duane Juniper Networks o +1 978 589 0551 m +1 603-770-7088 [email protected] -----Original Message----- From: Peter Wemm [mailto:[email protected]] Sent: Thursday, September 08, 2011 6:48 PM To: Peter Grehan Cc: Andrew Duane; [email protected]; [email protected] Subject: Re: Soliciting opinions on an extension of the bootinfo structure On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan <[email protected]> wrote: >> I'm proposing an extension framework for the bootinfo structure used >> to pass information from the bootstrap/loader to the kernel. Although >> I'm only proposing this for the MIPS bootinfo, it's completely >> applicable to any of them. >> >> What I propose is adding an optional platform extension structure: >> bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > Any reason not to put the vendor bits into another piece of loader metadata > ? That seems the extensible way to add additional info from the loader, > rather than extending bootinfo (as was the case pre-loader days). > > later, It sounds like they're not using loader, which is probably a reasonable thing for their environment. -- Peter Wemm - [email protected]; [email protected]; [email protected]; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[email protected]"
