Date: Thu, 15 May 1997 14:55:00 +0100 (BST) From: Mr M P Searle <csubl@csv.warwick.ac.uk> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: karpen@ocean.campus.luth.se, msmith@atrad.adelaide.edu.au, hackers@freebsd.org Subject: Re: 2.2 Splashkit Message-ID: <7018.199705151355@finnan.csv.warwick.ac.uk> In-Reply-To: <199705140124.KAA19577@genesis.atrad.adelaide.edu.au> from Michael Smith at "May 14, 97 10:54:37 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Mikael Karpberg stands accused of saying: > > > > > > 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? > > _Again_, the W95 logo.sys file is a 320x400 BMP image. > > > > 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. :-) > > It was? > > > > > 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. > > Er, have you ever heard of anything called "hardware abstraction" or > "layering"? > > Yeah, let's just go fiddle with the timer hardware inside the console > driver. I'm sorry; I don't think I'm quite up to the sort of abuse > that I'd get for that 8) > > > Am I correct? > > Er. "Yes you could", but "No I don't think I want to just now". > > Bruce will probably correct me, but I don't think that the kernel time > code is running during the hardware probe phase. > Well, I don't know much about the kernel probes, but most of the time is spent in delay loops, right? And although the timing of some of these may be important, if a loop is waiting for 2 seconds, it isn't going to matter if it delays for 2.1 seconds instead. So, the delay loop could be replaced by one which (if the delay is longer than, say, 50ms) is split into a number of short delay loops, with a call to the splash-screen routine in between. (Cycling the colours at the end of every device probe only wouldn't do much - on my machine at least the only devices that delay for a significant amount of time are the floppy, SCSI disk and SCSI CD.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7018.199705151355>