Date: Mon, 12 Sep 2011 08:46:15 -0400 From: Andrew Duane <aduane@juniper.net> To: John Baldwin <jhb@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Cc: "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: <AC6674AB7BC78549BB231821ABF7A9AEB74D5FF963@EMBX01-WF.jnpr.net> In-Reply-To: <201109090832.20770.jhb@freebsd.org> References: <AC6674AB7BC78549BB231821ABF7A9AEB748F9A329@EMBX01-WF.jnpr.net> <4E6940D3.4070801@freebsd.org> <CAGE5yCr1x2NB1pHYg6qPQPxFvWYA8bMus3gqM3nYkPCVbEpv8w@mail.gmail.com> <201109090832.20770.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Since this has turned out to be a more contentious idea than I thought, and= the upcoming FDT work will probably remove the need for it at all, I'm wit= hdrawing the idea. Although our current code uses such a platform extension= structure, we can make do with either metadata or environment variables fo= r the time being. =A0................................... Andrew Duane Juniper Networks o=A0=A0=A0+1 978 589 0551 m=A0 +1 603-770-7088 aduane@juniper.net =A0 -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org]=20 Sent: Friday, September 09, 2011 8:32 AM To: freebsd-arch@freebsd.org Cc: Peter Wemm; Peter Grehan; freebsd-hackers@freebsd.org; Andrew Duane Subject: Re: Soliciting opinions on an extension of the bootinfo structure 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=20 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, >=20 > 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 ar= ray=20 of variable length blobs appended after 'end'. Any boot loader can support adding metadata. --=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC6674AB7BC78549BB231821ABF7A9AEB74D5FF963>