From owner-freebsd-hackers  Wed May 14 01:45:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA24373
          for hackers-outgoing; Wed, 14 May 1997 01:45:25 -0700 (PDT)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24355
          for <hackers@FreeBSD.ORG>; Wed, 14 May 1997 01:45:22 -0700 (PDT)
Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id KAA05533; Wed, 14 May 1997 10:53:51 +0200 (MET DST)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199705140853.KAA05533@ocean.campus.luth.se>
Subject: Re: 2.2 Splashkit
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Wed, 14 May 1997 10:53:50 +0200 (MET DST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199705140124.KAA19577@genesis.atrad.adelaide.edu.au> from Michael Smith at "May 14, 97 10:54:37 am"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

According to Michael Smith:
> Mikael Karpberg stands accused of saying:
[...]
> > 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.

So there should be no problem, then? Someone (Terry?) said it was not quite
a BMP image, though. Maybe just a minor change.

[...]
> > 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)

:-) I'm just handing out design ideas, with wild guesses on implementation
details in them. I must confess I have a _very_ limited knowledge of the
kernel, and it's workings. There must be _some_ way of doing simple timing,
no? It wouldn't even need to be very exact.

> > Am I correct?
> 
> Er.  "Yes you could", but "No I don't think I want to just now".

Ah, that's a different matter. :-)
It's not worth messing up everything completely for, ofcourse. If it
is, however, not too hard to take timestamps, then it would make the
cycling look a lot nicer, probably.

  /Mikael