Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Sep 2011 08:20:21 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        Peter Grehan <grehan@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   Re: Soliciting opinions on an extension of the bootinfo structure
Message-ID:  <201109090820.21116.jhb@freebsd.org>
In-Reply-To: <4E6940D3.4070801@freebsd.org>
References:  <AC6674AB7BC78549BB231821ABF7A9AEB748F9A329@EMBX01-WF.jnpr.net> <4E6940D3.4070801@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, September 08, 2011 6:25:23 pm Peter Grehan 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).

I agree.  The metadata appended to the end of the kernel is a better way to
manage this.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201109090820.21116.jhb>