Subject: Re: mcclock_isa.c unification
To: None <firstname.lastname@example.org>
From: Izumi Tsutsui <email@example.com>
Date: 03/14/2006 01:46:11
In article <44159C68.firstname.lastname@example.org>
> I like the idea at least of having mcclock_common in dev/ic, and having
> bus- or machine-specific attachment code.
We already have dev/ic/mc146818.c, but it has a problem.
The mcclock also has an interval timer and some port (pmax)
uses it for timer (tick) interrupts but mc146818.c doesn't
take care of it. I have no idea how it should be handled in MI
We also have to consider how mips/mips_mcclock.c and releated
files should be rewriten. (should they be moved into arch/pmax?)