home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sys5.r4:1221 comp.unix.pc-clone.32bit:1013 comp.sys.ibm.pc.misc:16527
- Newsgroups: comp.unix.sys5.r4,comp.unix.pc-clone.32bit,comp.sys.ibm.pc.misc
- Path: sparky!uunet!noc.near.net!mv!jeck!smoke.marlboro.vt.us!jhood
- From: jhood@smoke.marlboro.vt.us (Lord Yertle)
- Subject: 386 device drivers: machine-independent I/O timing?
- Organization: Cthulhu Worship Meeting of Southern Vermont
- Date: Mon, 11 Jan 1993 12:02:30 GMT
- Message-ID: <1993Jan11.120230.1322@smoke.marlboro.vt.us>
- Lines: 20
-
-
- Sometime in the deep murky mists of time (within the last two years,
- anyway) somebody from Compaq or Dell posted an article about I/O
- delays in (I think) Unix device drivers. He suggested reading or
- writing some I/O port on the motherboard I/O bus to get ~ 1 us delays
- for I/O access timing, but I can't find the article (which I thought I
- saved) or remember what exactly he was suggesting.
-
- For the past few days, I've been wracking my brains over a fast
- printer driver (appearing soon on a net near you) that uses a core
- loop of assembler, at least on Xenix, and this info would be Good to
- Have. If anybody else out there saved the article, and actually still
- has it, could they mail me a copy? I'll repost it if there is
- interest...
-
- --jh
- --
- John Hood Cthulhu-- just imagine it!
- jhood@smoke.marlboro.vt.us
- Duke U, 1980: "Okay, so a few systems have the net started. What next?"
-