Port-sparc64 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Using %stick where available

So, I applied the patches to NetBSD 6 source, and compiled up my specific
kernel for the Sun Fire v240 and a GENERIC.UP for the Sun Netra T1 model 200,
and booted them. Both work, and the good timekeeping continues for the v240.

The Netra shows no change at all from unpatched source; same relatively poor
timekeeping. If there's a timecounter that is supposed to be recognized, it
was not:

% sysctl -a | egrep timec
kern.timecounter.choice = tick-counter(q=100, f=500000000 Hz) 
clockinterrupt(q=0, f=100 Hz) dummy(q=-1000000, f=1000000 Hz)
kern.timecounter.hardware = tick-counter

One thing I noticed that differs on the Netra between patch one and two: when
booting the first set of patches (which crashed late in the process - probably
at/near where timecounter selection is reported) is that during CPU probe
(near the top), the first set of patches caused the kernel to emit this:

cpu0: system tick frequency 11 MHz

So there's ... something there that they found.

        Erik <fair%netbsd.org@localhost>

Home | Main Index | Thread Index | Old Index