From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rdtsc to mili secs?
Date: Sun, 19 Nov 2000 22:46:23 +0100 [thread overview]
Message-ID: <20001119224623.A1418@suse.cz> (raw)
In-Reply-To: <3A078C65.B3C146EC@mira.net> <E13t7ht-0007Kv-00@the-village.bc.nu> <20001110154254.A33@bug.ucw.cz> <8uhps8$1tm$1@cesium.transmeta.com> <20001114222240.A1537@bug.ucw.cz> <3A12FA97.ACFF1577@transmeta.com> <20001116115730.A665@suse.cz> <20001118211231.A382@bug.ucw.cz> <20001118231354.A2796@suse.cz> <20001119212404.A1175@bug.ucw.cz>
In-Reply-To: <20001119212404.A1175@bug.ucw.cz>; from pavel@suse.cz on Sun, Nov 19, 2000 at 09:24:04PM +0100
On Sun, Nov 19, 2000 at 09:24:04PM +0100, Pavel Machek wrote:
> Hi!
>
> > > > Anyway, this should be solvable by checking for clock change in the
> > > > timer interrupt. This way we should be able to detect when the clock
> > > > went weird with a 10 ms accuracy. And compensate for that. It should be
> > > > possible to keep a 'reasonable' clock running even through the clock
> > > > changes, where reasonable means constantly growing and as close to real
> > > > time as 10 ms difference max.
> > > >
> > > > Yes, this is not perfect, but still keep every program quite happy and
> > > > running.
> > >
> > > No. Udelay has just gone wrong and your old ISA xxx card just crashed
> > > whole system. Oops.
> >
> > Yes. But can you do any better than that? Anyway, I wouldn't expect to
> > be able to put my old ISA cards into a recent notebook which fiddles
> > with the CPU speed (or STPCLK ratio).
>
> PCMCIA is just that: putting old ISA crap into modern hardware. Sorry.
Not really, fortunately. There are ISA-sytle NE2000's on PCMCIA, but
1) You know that you have a card there via the PCMCIA services and
2) They're not the old crappy NE2000's that'd die on a random read anyway.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-19 22:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-05 23:09 rdtsc to mili secs? Sushil Agarwal
2000-11-06 0:10 ` Andrea Arcangeli
2000-11-06 0:28 ` Alan Cox
2000-11-06 0:34 ` Andrea Arcangeli
2000-11-06 0:46 ` Alan Cox
2000-11-06 17:17 ` Anton Blanchard
2000-11-06 17:27 ` Alan Cox
2000-11-07 5:00 ` Antony Suter
2000-11-07 6:10 ` H. Peter Anvin
2000-11-07 12:18 ` Alan Cox
2000-11-10 14:42 ` Pavel Machek
2000-11-10 21:38 ` H. Peter Anvin
2000-11-10 22:23 ` Rogier Wolff
2000-11-10 23:00 ` H. Peter Anvin
2000-11-14 21:22 ` Pavel Machek
2000-11-15 21:05 ` H. Peter Anvin
2000-11-16 10:57 ` Vojtech Pavlik
2000-11-16 23:09 ` H. Peter Anvin
2000-11-18 20:13 ` Pavel Machek
2000-11-18 23:48 ` H. Peter Anvin
2000-11-19 9:21 ` Vojtech Pavlik
2000-11-18 20:12 ` Pavel Machek
2000-11-18 22:13 ` Vojtech Pavlik
2000-11-19 20:24 ` Pavel Machek
2000-11-19 21:46 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 8:15 ming_l
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=20001119224623.A1418@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.