From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Bradley Hanna <brahan.ml@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Programming the apic when no external to cpu timer is present?
Date: Sun, 10 Aug 2008 11:32:07 +0400 [thread overview]
Message-ID: <20080810073207.GB7249@lenovo> (raw)
In-Reply-To: <20080810072838.GA7249@lenovo>
[Cyrill Gorcunov - Sun, Aug 10, 2008 at 11:28:38AM +0400]
| [Bradley Hanna - Sat, Aug 09, 2008 at 08:19:43PM -0400]
| | I am working with an embedded testing board that has no timer external
| | to the cpu other than an rtc. How does linux go about programming the
| | local cpu timer (apic) to raise hardware interrupts?
| |
| | thanks for your patience,
| |
| | brahan
| |
|
| you could take a look on apic_(32|64).c. Here is the
| function you need I hope - setup_APIC_timer
|
| - Cyrill -
oops - it should be lapic_timer_setup :)
- Cyrill -
prev parent reply other threads:[~2008-08-10 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 0:19 Bradley Hanna
2008-08-10 7:28 ` Cyrill Gorcunov
2008-08-10 7:32 ` Cyrill Gorcunov [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=20080810073207.GB7249@lenovo \
--to=gorcunov@gmail.com \
--cc=brahan.ml@gmail.com \
--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®