From: Marco Roeland <marco.roeland@xs4all.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Alan Cox <alan@redhat.com>, Duncan Sands <baldrick@wanadoo.fr>
Subject: Re: Linux 2.5.65-ac2 (drivers/char/genrtc.c compile failure on i386)
Date: Sun, 23 Mar 2003 12:57:40 +0100 [thread overview]
Message-ID: <20030323115740.GA1104@localhost> (raw)
In-Reply-To: <Pine.GSO.4.21.0303231155380.9116-100000@vervain.sonytel.be>
On Sunday March 23rd 2003 at 11:58 uur Geert Uytterhoeven wrote:
> Oops, until last Friday I didn't even know genrtc was used on ia32...
>
> Anyway, can you please give this a try? I also updated PPC and PA-RISC, the
> other two known users of genrtc I forgot to update.
Ok. It compiles OK now (apart from some warnings for the janitors). I am
currently running 2.6.65-ac3 with it (well actually due to EXTRA_VERSION
still being -ac2 it thinks it is -ac2 ;-) To Alan from my phrase book:
"Peidiwch a gwneud hyn eto - pum punt o ddirwy!)
Only tested on i386, I still haven't decided whether a Power Mac is
worth the extra money, and my last HP machine was years ago ;-)
I don't seem to be a power genrtc user: I had to rmmod rtc before modprobe
genrtc succeeded but it does work:
$ cat /proc/driver/rtc
rtc_time : 11:49:52
rtc_date : 2003-03-23
rtc_epoch : 1900
alarm : 00:00:00
DST_enable : no
BCD : yes
24hr : yes
square_wave : no
alarm_IRQ : no
update_IRQ : no
periodic_IRQ : no
periodic_freq : 0
batt_status : okay
Thanks, Marco Roeland
prev parent reply other threads:[~2003-03-23 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 17:41 Linux 2.5.65-ac2 Alan Cox
2003-03-21 18:03 ` Christoph Hellwig
2003-03-21 18:10 ` Alan Cox
2003-03-21 21:03 ` Steven Cole
2003-03-22 20:22 ` Linux 2.5.65-ac2 (drivers/char/genrtc.c compile failure on i386) Marco Roeland
2003-03-23 10:58 ` Geert Uytterhoeven
2003-03-23 11:57 ` Marco Roeland [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=20030323115740.GA1104@localhost \
--to=marco.roeland@xs4all.nl \
--cc=alan@redhat.com \
--cc=baldrick@wanadoo.fr \
--cc=geert@linux-m68k.org \
--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