Re: x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Arnd Hannemann
Hi, Jordan Crouse schrieb: > On 23/01/08 23:11 +0100, Willy Tarreau wrote: >> Hi Peter, >> >> On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: >>> Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
incorrect case and inverted letters, but I try to refrain from whining, people say that I do it too much and for nothing :-) OK, here it comes updated. Willy >From 3a314dd5c2a694f5b0a1c1b8b5690ee28f711b5e Mon Sep 17 00:00:00 2001 From: Willy Tarreau <[EMAIL PROTECTED]> Date: Wed, 23 Jan 2008 23:05:50 +

Re: x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Jordan Crouse
On 23/01/08 23:11 +0100, Willy Tarreau wrote: > Hi Peter, > > On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: > > Willy Tarreau wrote: > > >The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards > > >run on a 32.768 kHz digital watch crystal. In practise, it will

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread H. Peter Anvin
Willy Tarreau wrote: Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: > Willy Tarreau wrote: > >The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards > >run on a 32.768 kHz digital watch crystal. In practise, it will not > >change the timer's frequency as the skew was only

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread H. Peter Anvin
Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the skew was only 2.4%, but it should provide more accurate intervals. - * Divisor Hz Min Delta

[PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the skew was only 2.4%, but it should provide more accurate intervals. Signed-off-by: Willy Tarreau <[EMAIL PROTECTED]> ---

[PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the skew was only 2.4%, but it should provide more accurate intervals. Signed-off-by: Willy Tarreau [EMAIL PROTECTED] ---

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread H. Peter Anvin
Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the skew was only 2.4%, but it should provide more accurate intervals. - * Divisor Hz Min Delta

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the skew was only 2.4%, but

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread H. Peter Anvin
Willy Tarreau wrote: Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency as the

Re: x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Jordan Crouse
On 23/01/08 23:11 +0100, Willy Tarreau wrote: Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change

Re: [PATCH 1/2] x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Willy Tarreau
: Willy Tarreau [EMAIL PROTECTED] Date: Wed, 23 Jan 2008 23:05:50 +0100 Subject: [PATCH 1/2] x86: GEODE fix MFGPT input clock value The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In practise, it will not change the timer's frequency

Re: x86: GEODE fix MFGPT input clock value

2008-01-23 Thread Arnd Hannemann
Hi, Jordan Crouse schrieb: On 23/01/08 23:11 +0100, Willy Tarreau wrote: Hi Peter, On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote: Willy Tarreau wrote: The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards run on a 32.768 kHz digital watch crystal. In