From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Real time clock on ia64 platforms
Date: Wed, 02 Jun 2004 06:26:53 +0000 [thread overview]
Message-ID: <40BD732D.6030709@hob.de> (raw)
In-Reply-To: <40BC3558.7040606@hob.de>
Alex Williamson schrieb:
>On Tue, 2004-06-01 at 01:50, Christian Hildner wrote:
>
>
>>Hi,
>>
>>someone may know what kind of RTC device the ia64 platforms (HP ZX 6000
>>+ i2000) use. I want to access it directly, without using EFI calls.
>>
>>
>
> This is strongly not recommended. On HP chipset boxes, the devices
>are only designed to be accessed via the EFI calls (and yes, EFI
>firmware can and does work around bugs in the RTC). There's also no
>architected way to find the real RTC in the address map.
>
So the only chance to access the rtc directly is to do it the same way
the firmware does. Since the firmware is that hardware specific it does
not need to "find" it because the firmware already knows where the rtc
is and how to access it. If the rtc is not mapped in the conventional
port address map, how does the firmware access it? Is there a
firmware-only accessible io memory map or is it done with machine
specific registers (msr)?
> Why do you
>need to poke it directly?
>
Because I need to call it from an environment, where no EFI calls are
possible. I know that the solution is absolutely not portable in any way
and in common it is bad doing that way but in that special case there is
no other way to go. And the portability is given at another layer on
top of it.
Christian
> Alex
>
next prev parent reply other threads:[~2004-06-02 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 7:50 Real time clock on ia64 platforms Christian Hildner
2004-06-01 16:21 ` Matthew Wilcox
2004-06-01 16:40 ` Alex Williamson
2004-06-01 17:22 ` Christoph Lameter
2004-06-02 5:56 ` Christian Hildner
2004-06-02 6:04 ` Stephane Eranian
2004-06-02 6:26 ` Christian Hildner [this message]
2004-06-02 6:41 ` Christian Hildner
2004-06-02 6:51 ` Stephane Eranian
2004-06-02 7:01 ` Christian Hildner
2004-06-02 7:14 ` Stephane Eranian
2004-06-02 7:22 ` Robin Holt
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=40BD732D.6030709@hob.de \
--to=christian.hildner@hob.de \
--cc=linux-ia64@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