From: David Brownell <david-b@pacbell.net>
To: linux@bohmer.net
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: gtod/clocksource/clockevents documentation
Date: Sun, 22 Apr 2007 11:13:21 -0700 [thread overview]
Message-ID: <200704221113.21778.david-b@pacbell.net> (raw)
In-Reply-To: <3efb10970704220900m53874769ta8f540098ea7d9de@mail.gmail.com>
On Sunday 22 April 2007, Remy Bohmer wrote:
> Hello David,
>
> Thanks for this patch you sent me. This patch will also increase the
> clock resolution which is good in RT context.
Yeah, a 32768 Hz timer (battery backed) may leave a bit to be desired.
> But, unfortunately, I have some problems with compiling the kernel, as
> this patch does not enable CONFIG_GENERIC_TIME, while the patch you
> published earlier did.
I'm not sure which patch you mean. I tested only in conjunction with
updates specific to the at91rm9200.
> Is there a special reason why you removed that?
My config didn't need it ... and ISTR that making a system support
it was more than just adding a "select GENERIC_TIME" after
> > +config AT91_TC_CLOCKSOURCE
Like the various arch/arm/kernel/* changes needed. ISTR
there are several still in Russell's patch queue.
But basically, because I couldn't test such an at91sam926x
configuration. That would be one of the "tweaks" that I
mentioned you would need to do.
- Dave
next prev parent reply other threads:[~2007-04-22 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 21:14 gtod/clocksource/clockevents documentation Remy Bohmer
2007-04-21 23:00 ` David Brownell
2007-04-22 16:00 ` Remy Bohmer
2007-04-22 18:13 ` David Brownell [this message]
2007-04-22 18:47 ` Remy Bohmer
2007-04-23 11:44 ` Nicolas Ferre
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=200704221113.21778.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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