From owner-freebsd-hackers Fri Nov 7 09:59:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13079 for hackers-outgoing; Fri, 7 Nov 1997 09:59:34 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA13068 for ; Fri, 7 Nov 1997 09:59:23 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA27137; Fri, 7 Nov 1997 17:48:08 +0100 From: Luigi Rizzo Message-Id: <199711071648.RAA27137@labinfo.iet.unipi.it> Subject: Re: Inter outb() timing To: jamil@trojanhorse.ml.org (Jamil J. Weatherbee) Date: Fri, 7 Nov 1997 17:48:07 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Nov 7, 97 09:16:23 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If I do a: > > outb (0x300, 0x00); > outb (0x300, 0xff); > outb (0x300, 0x00); > > How long should 0xff appear at that address? assuming that: - your process is not pre-empted in the middle of the sequence; - you don't get a page fault before the last instruction; - your processor is fast enough that reading the next instruction does not cause stalls (yes there are still 386sx-16 serving us...) ; then probably the time depends on the configuration of the ISA bus on your machine (clock, wait states), and you might observe a time in the 200..800ns range. Cheers Luigi