re-programming the 8253 Timer chip wouldn't jeoperdize the OS ?

Article View: comp.os.os2.programmer

Article #2104

Back to comp.os.os2.programmer Previous Next

#2104

From: chaibp
Date: Fri, 16 Oct 1992 05:13

7 lines
933 bytes

If a device driver re-programmes the 8253 Timer chip (e.g. changing its mode
from the default mode 3 to mode 2 or changing its interrupt frequency), 
why wouldn't the OS be jeoperdized ? At least I would expect the OS 
scheduling and disk access be affected because all these functions 
are based on the timer. But apparently none of these is affected at all 
with a timing program that I got hold of from ftp-os2.nmsu.edu under
/pub/os2/2.0/ibm. Why ?

Technical Details

Message-ID: <1992Oct16.051352.12116@nuscc.nus.sg>

Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!jvnc.net!nuscc!CHAIBP@iscs.nus.sg

Show Full Headers

Complete Article Headers

Newsgroups: comp.os.os2.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!jvnc.net!nuscc!CHAIBP@iscs.nus.sg
From: chaibp@iscs.nus.sg
Subject: re-programming the 8253 Timer chip wouldn't jeoperdize the OS ?
Message-ID: <1992Oct16.051352.12116@nuscc.nus.sg>
Sender: usenet@nuscc.nus.sg
Reply-To: CHAIBP@NUSDISCS.BITNET
Organization: Dept. of Information Systems and Computer Science, National University of Singapore
Date: Fri, 16 Oct 1992 05:13:52 GMT
Lines: 8