On Tue, 2010-10-19 at 13:10 -0500, pacman@kosh.dhis.org wrote:

So what type of driver, firmware, or hardware bug puts a 16-bit 1000Hz
timer
in memory, and does it in little-endian instead of the CPU's native
byte
order? And why does it stop doing it some time during the early init
scripts,
shortly after the root filesystem fsck?

I have not yet attempted to repeat the experiment. If it is
repeatable, I'll
probe more deeply into those init scripts later. I'm looking hard at
/etc/rcS.d/S11hwclock.sh 

Stinks of USB...

Ben.