mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Remy Bohmer" <l.pinguin@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"David Brownell" <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: gtod/clocksource/clockevents documentation
Date: Sat, 21 Apr 2007 23:14:22 +0200	[thread overview]
Message-ID: <3efb10970704211414q7c66c154m79cc06db61eb76be@mail.gmail.com> (raw)

Hello All,

I need to implement a gtod/clocksource/clockevents implementation for
the Atmel ARM AT91SAM9261 CPU, and I am looking for some kernel
(interface) documentation about these mechanisms.

I already investigated the 'examples'/implementations of other
architectures in the kernel, but that did not really help me... I also
looked at the patch for the AT91RM9200 CPU posted by David Brownell...
I hacked something which now makes the RT kernel to boot, but the
time-of-day warps several minutes per second, back and forward in
time... ;-)

So, Can anybody please give me pointer to some useful documentation
and/or examples?

The reason behind this initiative is to make the RT-preempt patch
compile and work on this architecture. Currently the GENERIC_TIME is
not set, which results in several unresolved externals at compile
time, and I believe the best way to fix this is to implement proper
gtod/clocksource/clockevents to allow the enabling of GENERIC_TIME

Kind Regards,

Remy Böhmer

             reply	other threads:[~2007-04-21 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21 21:14 Remy Bohmer [this message]
2007-04-21 23:00 ` David Brownell
2007-04-22 16:00   ` Remy Bohmer
2007-04-22 18:13     ` David Brownell
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=3efb10970704211414q7c66c154m79cc06db61eb76be@mail.gmail.com \
    --to=l.pinguin@gmail.com \
    --cc=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
all inboxes | Powered by JetHome®