home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!destroyer!cs.ubc.ca!unixg.ubc.ca!ochealth
- From: ochealth@unixg.ubc.ca (ochealth)
- Newsgroups: comp.os.os2.misc
- Subject: Re: how can you have a 32 bit display driver?
- Date: 6 Nov 1992 06:21:28 GMT
- Organization: University of British Columbia, Vancouver, B.C., Canada
- Lines: 33
- Message-ID: <1dd2t8INNbll@iskut.ucs.ubc.ca>
- References: <1dbugtINN509@gap.caltech.edu>
- NNTP-Posting-Host: unixg.ubc.ca
-
- In article <1dbugtINN509@gap.caltech.edu> hacker@cco.caltech.edu (Jonathan Bruce Hacker) writes:
- >
- >disclaimer: I know nothing about writing display drivers.
- >
- >I do know that an ISA bus is 16 bit. Therefore, does it not follow
- >that for a display adapter plugged into an ISA bus, it is defacto 16
- >bit and can never be 32 bit? So, how do you write a 32 bit driver for
- >a 16 bit piece of hardware?
- >
- >
- by that logic, the i386sx microprocessor should be incapable of running
- 32 bit software, because it has a 16 bit data bus.
-
- A 32 bit driver is one that is written using the "real" i386 instructions,
- that operate with 32 bit registers and opcodes. The ISA bus happens to
- be 16 bits wide, but that has nothing to do with the code in the CPU that
- operates on the bus. The fact that it is 16 bits wide is a hardware problem,
- the hardware logic will require twice as many bus cycles to send a 32 bit
- word across it, as a 32 bit bus would require.
-
- >
- >
- >--
- >Jon Hacker
- >Caltech, Pasadena CA
- >hacker@tumbler-ridge.caltech.edu
-
-
- --
- ______________________________________________________________________________
- jpm: ochealth@unixg.ubc.ca
- Happily using OS/2 2.0 because MS Windows isNT ___
- Insert VapourFeature ^^^
-