Subject: Re: next68k port status?
To: None <port-next68k@NetBSD.org>
From: gabriel rosenkoetter <email@example.com>
Date: 10/15/2003 17:06:49
Content-Type: text/plain; charset=us-ascii
On Wed, Oct 15, 2003 at 09:03:02PM +0200, Manuel Bouyer wrote:
> I don't know, what's the problem with mac68k ?
mac68ks lose a massive amount of time during disk access, because
clock interrupts are at a lower--or the same?--priority as I/O
interrupts, so they get postponed till after the I/O is done. My
understanding is that this is true under any OS, but Mac OS shows it
a bit less by cheating and guessing how long it took to do a disk
> Here the date is always in 1932 when booting (which breacks a lot of thin=
> because it's a negative time_t)
You sure that's not just a dead clock battery?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----