From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Benjamin Herrenschmidt <bh40@calva.net>,
martin costabel <costabel@wanadoo.fr>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: rtc again...
Date: Thu, 03 Aug 2000 10:56:55 +0100 [thread overview]
Message-ID: <200008030957.KAA17120@hyperion.valhalla.net> (raw)
and the 2.2.17pre15 dmesg contains the lines:
====
Linux version 2.2.17pre15-ben1-snd (root@athena) (gcc version 2.95.2
19991024 (release/franzo)) #2 Wed Aug 2 23:16:52 BST 2000
[...]
pmac nvram is core99: 0
System has 64 possible interrupts
GMT Delta read from XPRAM: 60 minutes, DST: on
====
which, as I said, works as long as RTC is -not- involved.
are we applying a correct twice?
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-03 9:56 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 9:56 Iain Sandoe [this message]
2000-08-03 10:13 ` rtc again Benjamin Herrenschmidt
2000-08-03 11:58 ` Martin Costabel
2000-08-03 12:28 ` initscript logging (was rtc again...) Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2000-08-08 14:31 rtc again Iain Sandoe
2000-08-08 17:08 ` Michael Schmitz
2000-08-08 17:41 ` Benjamin Herrenschmidt
2000-08-08 22:44 ` Gabriel Paubert
2000-08-09 8:44 ` Benjamin Herrenschmidt
2000-08-09 11:32 ` Martin Costabel
2000-08-09 13:50 ` Gabriel Paubert
2000-08-09 15:25 ` Benjamin Herrenschmidt
2000-08-09 16:54 ` Takashi Oe
2000-08-09 17:04 ` Benjamin Herrenschmidt
2000-08-09 23:12 ` Takashi Oe
2000-08-09 23:48 ` Benjamin Herrenschmidt
2000-08-09 22:13 ` Gabriel Paubert
2000-08-09 22:48 ` Benjamin Herrenschmidt
2000-08-10 3:08 ` Gabriel Paubert
2000-08-10 0:00 ` William Blew
2000-08-09 14:26 ` Takashi Oe
2000-08-09 0:55 ` Takashi Oe
2000-08-09 8:48 ` Benjamin Herrenschmidt
2000-08-09 16:37 ` Takashi Oe
2000-08-09 22:46 ` Gabriel Paubert
2000-08-09 14:24 ` Geert Uytterhoeven
2000-08-08 11:35 Iain Sandoe
2000-08-08 13:14 ` Geert Uytterhoeven
[not found] <20000804205524.383@192.168.1.10>
2000-08-05 1:10 ` Takashi Oe
2000-08-05 11:25 ` Benjamin Herrenschmidt
2000-08-05 14:44 ` Takashi Oe
2000-08-03 11:24 Iain Sandoe
2000-08-03 9:41 Iain Sandoe
2000-08-02 22:48 Iain Sandoe
2000-08-03 9:00 ` Martin Costabel
2000-08-03 9:30 ` Benjamin Herrenschmidt
2000-08-03 10:54 ` Gabriel Paubert
2000-08-03 11:14 ` Benjamin Herrenschmidt
2000-08-03 11:25 ` Gabriel Paubert
2000-08-03 11:45 ` Gabriel Paubert
2000-08-03 13:25 ` Benjamin Herrenschmidt
2000-08-03 23:33 ` Takashi Oe
2000-08-04 8:55 ` Gabriel Paubert
2000-08-04 15:25 ` David Edelsohn
2000-08-04 15:50 ` Benjamin Herrenschmidt
2000-08-07 12:33 ` Gabriel Paubert
2000-08-07 11:51 ` Gabriel Paubert
2000-08-07 13:18 ` Benjamin Herrenschmidt
2000-08-07 15:14 ` David Edelsohn
2000-08-07 21:16 ` Gabriel Paubert
2000-08-08 1:39 ` Paul Mackerras
2000-08-11 11:04 ` Gabriel Paubert
2000-08-12 6:29 ` Paul Mackerras
2000-08-12 12:02 ` Ethan Benson
2000-08-12 12:51 ` Gabriel Paubert
2000-08-12 18:46 ` Gabriel Paubert
2000-08-14 12:59 ` Gabriel Paubert
[not found] ` <Pine.LNX.3.96LJ1.1b7.1000803182949.650C-100000@ofey.earthl ink.net>
2000-08-03 23:58 ` Franz Sirl
2000-08-04 0:33 ` Takashi Oe
2000-08-04 12:54 ` Benjamin Herrenschmidt
2000-08-04 13:40 ` Takashi Oe
2000-08-04 13:20 ` Geert Uytterhoeven
2000-08-08 11:20 ` Gabriel Paubert
2000-08-03 10:31 ` Franz Sirl
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=200008030957.KAA17120@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bh40@calva.net \
--cc=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.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.