From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] RTC support on ia64
Date: Tue, 17 Dec 2002 21:57:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805603@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805600@msgid-missing>
>>>>> "Alex" = Alex Williamson <alex_williamson@hp.com> writes:
Alex> Joel, Does this provide more functionality than the EFI RTC?
Alex> Concerns I have w/ it on ia64 is that the rtc driver assumes you
Alex> have a legacy rtc at the legacy irq and port address. This
Alex> won't work on HP zx1 boxes, the legacy hardware doesn't exist.
Alex> In the future, there's a possibility that the port address could
Alex> be allocated to non-legacy purposes. Maybe ACPI could tell you
Alex> if you have a legacy RTC, it could at least tell you if you
Alex> support PC/AT compatible interrupts. Thanks,
Yes it does. There's no way to get a regular interrupt into user
space from the EFI RTC.
I've been using the PMU to generate regular interrupts, and have a
locally-modified amlat benchmark that does that.
--
Dr Peter Chubb peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
next prev parent reply other threads:[~2002-12-17 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 16:26 [Linux-ia64] RTC support on ia64 Joel GUILLET
2002-12-17 20:13 ` Alex Williamson
2002-12-17 21:57 ` Peter Chubb [this message]
2002-12-17 23:57 ` David Mosberger
2002-12-18 15:01 ` Joel GUILLET
2002-12-18 18:18 ` Stephane Eranian
2002-12-18 19:26 ` Alex Williamson
2003-07-01 6:11 ` Zhu, Yi
2003-07-01 6:11 ` Zhu, Yi
2003-07-01 12:15 ` Eric Piel
2003-07-01 22:53 ` Peter Chubb
2003-07-02 0:45 ` Zhu, Yi
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=marc-linux-ia64-105590709805603@msgid-missing \
--to=peter@chubb.wattle.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.