home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!cs.utexas.edu!chinacat!chip
- From: chip@chinacat.unicom.com (Chip Rosenthal)
- Subject: Re: Avoiding the "8/16 Bit Problem"
- Organization: Unicom Systems Development, Austin, TX
- Date: Wed, 26 Aug 1992 23:31:35 GMT
- Message-ID: <1992Aug26.233135.11289@chinacat.unicom.com>
- References: <18392@polstra.UUCP> <1992Aug26.145710.3533@crd.ge.com>
- Lines: 27
-
- In article <1992Aug26.145710.3533@crd.ge.com>
- davidsen@crd.ge.com (bill davidsen) writes:
- > The real 1542 is a 16 bit card, won't run in 8 bit sockets.
-
- But that's beside the point.
-
- The issue on the 8-bit vs 16-bit conflict is how the device performs
- memory accesses. For example, a card might do 16-bit I/O accesses
- but only 8-bit memory accesses. In the context of this question, such
- a card should be treated as an 8-bit card even though it requires a
- 16-bit slot.
-
- The specific question which needs to be asked is whether the SCSI card
- uses 8-bit or 16-bit BIOS ROM accesses, because that is the only memory
- mapped portion of these cards. True, UNIX does not use the BIOS, but
- that doesn't matter. The whole point is that if any card in the 128K
- memory segment wants to do memory transfers 16-bits at a time, then
- every card in that segment must use 16-bit tranfers.
-
- I don't know the answer to the question, but I'd guess with 99% confidence
- that you are right, and the SCSI card does 16-bit memory accesses.
-
- Yes, it's a stupid restriction. Yes, it's typical IBM engineering.
- --
- Chip Rosenthal 512-482-8260 | The secret to a long life is
- Unicom Systems Development | knowing when it's time to go.
- <chip@chinacat.Unicom.COM> | - Michelle Shocked
-