Date: Fri, 9 Sep 2011 08:32:20 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-arch@freebsd.org Cc: Andrew Duane <aduane@juniper.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Peter Grehan <grehan@freebsd.org> Subject: Re: Soliciting opinions on an extension of the bootinfo structure Message-ID: <201109090832.20770.jhb@freebsd.org> In-Reply-To: <CAGE5yCr1x2NB1pHYg6qPQPxFvWYA8bMus3gqM3nYkPCVbEpv8w@mail.gmail.com> References: <AC6674AB7BC78549BB231821ABF7A9AEB748F9A329@EMBX01-WF.jnpr.net> <4E6940D3.4070801@freebsd.org> <CAGE5yCr1x2NB1pHYg6qPQPxFvWYA8bMus3gqM3nYkPCVbEpv8w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, September 08, 2011 6:48:19 pm Peter Wemm wrote: > On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan <grehan@freebsd.org> 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. That doesn't stop you from adding metadata to the kernel. It is just an array of variable length blobs appended after 'end'. Any boot loader can support adding metadata. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201109090832.20770.jhb>