Izumi Tsutsui wrote:
> In article <44159C68.3040904@tadpole.com>
> garrett_damore@tadpole.com wrote:
>
>   
>> 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
> code yet.
>   
Hmm... maybe this warrants adding some code the MI routine.  I've not
looked at the driver myself yet, but just adding some functions which MD
code could call seems like a step in the right direction.

> We also have to consider how mips/mips_mcclock.c and releated
> files should be rewriten. (should they be moved into arch/pmax?)
>   

Don't know the answer to this.  :-)

    -- Garrett
> ---
> Izumi Tsutsui
>   


-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191