From: Rene Herman <rene.herman@keyaccess.nl>
To: Russ Anderson <rja@sgi.com>
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
Jack Steiner <steiner@sgi.com>
Subject: Re: [patch] x86 BIOS interface for RTC on SGI UV
Date: Wed, 09 Jul 2008 23:47:57 +0200 [thread overview]
Message-ID: <4875320D.2070306@keyaccess.nl> (raw)
In-Reply-To: <20080709213622.GC22744@sgi.com>
On 09-07-08 23:36, Russ Anderson wrote:
>> ... and wouldn't uv_bios_strerror/uv_bios_freq_base be better names?
>
> The plan is for both x86 and ia64 versions of uv, with this being
> the x86 version. The ia64 version has ia64_sal_strerror()
> and ia64_sal_freq_base(). Hence the x86_bios_* naming convention.
> I'm not strongly tied to that convention, it just seemed logical.
Ah, I see. Not much of an opinion then. x86_bios sounds a bit generic,
but whatever...
> Here is the updated patch.
[ ... ]
> +enum {
> + BIOS_STATUS_SUCCESS = 0,
> + BIOS_STATUS_UNIMPLEMENTED = -1,
> + BIOS_STATUS_EINVAL = -2,
> + BIOS_STATUS_ERROR = -3
> +};
[ .. ]
> +extern long
> +x86_bios_freq_base(unsigned long which, unsigned long *ticks_per_second,
> + unsigned long *drift_info);
> +static __init void uv_rtc_init(void)
> +{
> + unsigned long status, ticks_per_sec, drift;
*status* should remain a long :-)
Rene.
next prev parent reply other threads:[~2008-07-09 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 20:27 [patch] x86 BIOS interface for RTC on SGI UV Russ Anderson
2008-07-09 20:58 ` Rene Herman
2008-07-09 21:36 ` Russ Anderson
2008-07-09 21:47 ` Rene Herman [this message]
2008-07-09 22:09 ` Russ Anderson
2008-07-09 22:54 ` Rene Herman
2008-07-10 1:44 ` H. Peter Anvin
2008-07-10 14:54 ` Russ Anderson
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=4875320D.2070306@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rja@sgi.com \
--cc=steiner@sgi.com \
--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 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.