Re: RTC drift in PPC

2007-06-05 Thread Theo Gjaltema
I 'v measured the clock on a mpc8280 board running the 2.4.25 kernel 
obtained from ELDK3.1.1, no problem with the clock during a test period 
of a few days.

Theo.
 We are running RTC on mpc860 board with external crystal...
 We are getting 4 minutes drift for 21 hours.
 

 A slowdown in the approx. range 1:300 to 1:350 is endemic to linux ppc:
 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157581

   

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Re: Linux interrupt managing on 8xx

2007-06-05 Thread Ricardo Scop
On Monday 04 June 2007 17:37, DI BACCO ANTONIO - technolabs wrote:
 I have a component named pca9555 (on the i2c bus) that is an I/O expander.
 It can generate an interrupt to the MPC8xx processor (SIU_IRQ1 pin). This
 pin will be active till I read registers of pca9555. Because I cannot
 access the i2c bus in the interrupt handler I queue a work on a work queue.
 Just at the end of the interrupt handler  should I disable the interrupt on
 the mpc8xx? I think that otherwise the interrupt will pop up again till I
 execute the work in the work queue finally reading the pca9555 and shutting
 off the source of the interrupt.

Well, why don't you simply program the interrupt to be edge-triggered in the 
SIEL register? This way it will only occur again after the pin level is 
cleared.

HTH,

Ricardo.
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded