From: Lennert Buytenhek <buytenh@wantstofly.org>
To: John Bowler <jbowler@acm.org>
Cc: "'Deepak Saxena'" <dsaxena@plexity.net>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] 2.6.14 include/asm-arm/arch-ixp4xx/timex.h: fix clock frequency on NSLU2
Date: Fri, 28 Oct 2005 10:32:45 +0200 [thread overview]
Message-ID: <20051028083245.GB26901@xi.wantstofly.org> (raw)
In-Reply-To: <001101c5db89$5d5b1560$1001a8c0@kalmiopsis>
John,
On Thu, Oct 27, 2005 at 11:32:25PM -0700, John Bowler wrote:
> The problem is that the NSLU2 deviates from the Intel IXDP425
> system by using a cystal with frequency 66MHz as opposed to the
> Intel stated (not quite mandated) value of 66.666666MHz. This
> results in serious errors in the RTC (1%).
>
> The patch configs in the correct value for the NSLU2. The problem
> with the patch is that a multi-config kernel which includes NSLU2
> support will use the NSLU2 frequency. However such kernels are
> not a requirement as generic kernels are never flashed into NSLU2
> systems (so there is no need to build NSLU2 support into a generic
> kernel).
As previously stated: with this patch, compiling in support for the
NSLU2 will make the timer tick base right for the NSLU2 but wrong
for everything else.
There are two ways of dealing with this problem:
1/ The patch you sent, plus some config hacks to make it impossible
to compile in NSLU2 support together with support for another ixp4xx
machine type that has FREQ=66666666, sidestepping the issue; or
2/ Make the ixp4xx timer tick base runtime selectable altogether, for
example with the patch that I sent to linux-arm-kernel a while ago.
I'm not very much in favor of 1/, but at least it's better than not
having any kind of protection at all. If you leave it to the user,
they simply _are_ going to get it messed up.
--L
prev parent reply other threads:[~2005-10-28 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 6:32 John Bowler
2005-10-28 8:32 ` Lennert Buytenhek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051028083245.GB26901@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=dsaxena@plexity.net \
--cc=jbowler@acm.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®