Date: Tue, 13 May 1997 18:07:02 +0200 (MET DST) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hackers@FreeBSD.ORG Subject: Re: 2.2 Splashkit Message-ID: <199705131607.SAA27604@ocean.campus.luth.se> In-Reply-To: <199705131042.UAA16674@genesis.atrad.adelaide.edu.au> from Michael Smith at "May 13, 97 08:12:05 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Michael Smith:
> Mikael Karpberg stands accused of saying:
> >
> > Really... IMHO that would kinda suck (both of the above).
> > Although, with a small modification, it would be really nice.
>
> "what is possible sucks, but my impossible fantasy would be just wonderful".
Actually:
"Those two ideas suck, but my impossible fantasy would be just wonderful". :)
That is, don't make it stick after booting. (bad idea number one)
Also, don't make it come back as a screen saver. (bad idea number two)
Reason: It should be something to have there while booting, like a nice
"Please wait while I boot thing thing" text. After you've booted, it wont fit.
A screensaver (as a suggested later in my mail) should use a picture of its
own (which COULD be the same, if you had a fitting boot picture).
Making it dissapear after botting is done, and then never come back is not
impossible at all.
> > How about this:
> >
> > The splash screen should use an image ("/splash.pic" ?) that used the exact
> > logo.sys format. That would make it easy to use finished slashes out there,
>
> We have already noted that the "finished" splash image is a 320x400
> bmp file, as currently (partially) supported.
Umm... Is this a "no, silly. we allready use another format" or not?
I have no idea what format the logo.sys uses. But if we want to get color
cycling in, etc, anyway... Is there a problem with using their format?
What, in that case?
> > without having to use some converter. It should be easy to read and put in
> > memory in any format you like it, no? That would make things like
> > "ln -s /dos/logo.sys /splash.pic" work too.
>
> Symlinks are right out. The file will have to be present, in place,
> in the root filesystem, in order to be read by the bootloader.
Ack! Right. Oh well... was a nice thought. :-)
> > Color cycling should happen at an even pace, if possible. I'm not sure if
>
> It's already been explained that it can't.
Umm... No. It was said that there was a timer interupt, but that it was not
available during probing, and so you (ie "syscons") would have to wait for
driver output and possibly do something at the same time as you output that.
So every time you get a call from a driver, you should be able to cycle the
colors. What you will want to do, however, is not cycle too often. So you
save the value of the hardware clock, or something, each time you cycle.
Then when you get a call from a driver (or an interput, when those are
on), you check if the splashscreen is up, and if so, check if at least X
milliseconds past since that timestamp. If so, you get a new timestamp,
cycle the colors, and continue with what you were suposed to. If not, you
just do what you were suposed to. That way it wont cycle super fast when the
boot scrolls pretty quickly. And the cycle can be made pretty slow so that
"hangs" (times some driver prints nothing, while waiting for devices to
answer, or so) isn't noticed as much. That way you get a fairly even cycling.
Am I correct?
/Mikael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705131607.SAA27604>