Subject: Re: RFC: vesafb, splash screen, and rasops shadowfb patch
To: Bill Studenmund <wrstuden@netbsd.org>
From: Jared D. McNeill <jmcneill@invisible.ca>
List: tech-kern
Date: 02/14/2006 11:55:05
On Tue, 2006-02-14 at 11:51 -0800, Bill Studenmund wrote:
> On Tue, Feb 14, 2006 at 11:40:46AM -0400, Jared D. McNeill wrote:
> > On Tue, 2006-02-14 at 20:26 +0100, Jachym Holecek wrote:
> > > While going with GIMP + .h is the easiest solution, something like
> > > what mdsetimage(8) does would probably be better -- you could then
> > > change splashscreen image w/o kernel recompile.
> > 
> > I was under the impression that the md didn't attach until much later in
> > the boot process.
> 
> I think the idea was that you'd have a tool that would inject the image 
> into an existing kernel. Not that you would have the image in the file 
> system that mdsetimage injected.

Changing the checksum of the kernel image without recompiling has always
made me uncomfortable. How often do people plan on changing their splash
screen?

I would be happy with __initdata functionality similar to that of Linux
(as Jachym mentioned, this is a huge win for more than just the splash
image). Another (MD, unfortunately) option would be for boot2 to read an
image from disk, load it into memory, and pass the physical address to
the kernel at startup.

Cheers,
Jared