From: Willy Tarreau <willy@w.ods.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: root@chaos.analogic.com, Willy Tarreau <willy@w.ods.org>,
Jim Paris <jim@jtan.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: time() glitch on 2.4.18: solved
Date: Tue, 5 Nov 2002 21:14:38 +0100 [thread overview]
Message-ID: <20021105201438.GA26116@alpha.home.local> (raw)
In-Reply-To: <1036526846.6750.12.camel@irongate.swansea.linux.org.uk>
On Tue, Nov 05, 2002 at 08:07:26PM +0000, Alan Cox wrote:
> On Tue, 2002-11-05 at 19:29, Richard B. Johnson wrote:
> > The only hardware a modern PC needs to use "slow-down_io" on is
> > the RTC CMOS device. Since we need to support older boards, you
> > don't want to remove the _p options indiscriminately, but you do
> > not want them ever between two consecutive writes to the same device-
> > port.
>
> I own at least one that needs the _p on the DMA controller and at one
> that needs _p on the PIT
Well, in fact, Intel's 82C54 datasheet says that this chip needs at least
165 ns between two consecutive operations, either read or write. So with a
8 Mhz bus, you may effectively need to insert fake accesses, although most
modern chipsets certainly have better specs.
But the spec clearly states that you can interleave accesses to other
counters between the first and second bytes without problem, so good
implementations should see no side effect.
Richard, if your PIT doesn't support accesses to port 80, could you try to
use other ports ?
Cheers,
Willy
next prev parent reply other threads:[~2002-11-05 20:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 6:37 time() glitch on 2.4.18 at 177 days uptime? Jim Paris
2002-11-03 19:32 ` time() glitch on 2.4.18: solved Jim Paris
2002-11-03 20:30 ` Alan Cox
2002-11-05 16:30 ` [PATCH] " Jim Paris
2002-11-05 16:54 ` george anzinger
2002-11-05 17:10 ` Willy Tarreau
2002-11-05 18:16 ` Alan Cox
2002-11-05 18:02 ` Jim Paris
2002-11-05 18:37 ` Alan Cox
2002-11-05 18:20 ` Willy Tarreau
2002-11-05 18:50 ` Jim Paris
2002-11-05 17:14 ` Willy Tarreau
2002-11-05 17:42 ` Jim Paris
2002-11-05 18:57 ` Richard B. Johnson
2002-11-05 19:08 ` Willy Tarreau
2002-11-05 19:29 ` Richard B. Johnson
2002-11-05 20:07 ` Alan Cox
2002-11-05 20:14 ` Willy Tarreau [this message]
2002-11-05 20:38 ` Richard B. Johnson
2002-11-05 23:15 ` Willy Tarreau
2002-11-06 12:47 ` Richard B. Johnson
2002-11-06 13:25 ` Alan Cox
2002-11-06 23:21 ` Jim Paris
2002-11-05 20:23 ` Richard B. Johnson
2002-11-05 20:57 ` Alan Cox
2002-11-05 20:41 ` Richard B. Johnson
2002-11-06 15:09 ` Christer Weinigel
2002-11-06 15:49 ` Richard B. Johnson
2002-11-05 20:06 ` Alan Cox
2002-11-05 17:32 ` Alan Cox
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=20021105201438.GA26116@alpha.home.local \
--to=willy@w.ods.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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.