Subject: Re: mvme68k timecounters.... untested
To: None <email@example.com>
From: Izumi Tsutsui <firstname.lastname@example.org>
Date: 09/17/2006 17:16:56
> > Anyway, "pcc_timer_hz2lin(100)" macro is better.
> Maybe. But the 0x10000 has to stand, because the counter counts _up_
> from PCC_TIMER100HZ and ticks when it overflows to 0. I think the macro
> PCC_TIMER100HZ is actually easier to read, but I'm not terribly "close"
> to this platform.
Hmm. pcc_timer_hz2lin() macro should use 0x10000 rather than 65536?
Anyway, it isn't so important on this change so both are ok for me.
> > Probably you also have to apply the similar changes against
> > sys/dev/mvme/clock_pcctwo.c. (shared with mvmeppc. umm)
> Really? I know nothing about VME, really. Should this driver be
Ah, it isn't shared *yet*, but log messages said:
>> Separate out devices common to many Motorola mvme boards (68k, 88k and ppc)
>> in preparation for future mvmeppc and mvme88k ports.
>> This needs a bit if tidying up to make it trully shareable, which will
>> happen as the new mvme ports are added.
Anyway, according to autoconf.c and GENERIC, MVME14x has pcc
and MVME16x and MVME17x boards have pcctwo (which is in sys/dev/mvme).