Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: 8-bit xfer to 16-bit memory
Message-ID: <2689@sixhub.UUCP>
Date: 19 Dec 90 22:56:05 GMT
References: <1990Dec14.195053.5270@amd.com> <1802@gold.gvg.tek.com> <1990Dec17.171123.18719@amd.com>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 17

In article <1990Dec17.171123.18719@amd.com> phil@brahms.amd.com (Phil Ngai) writes:

| Right, but that's not what I'm asking about. I'm asking about an
| 8-bit access to a 16-bit memory which does yank on MEMCS16*.
| Solari indicates it should run at 8-bit speeds even though we
| know it's a 16-bit device. 
| 
| Why?

  I think the CPU and memory have to both agree it's 16 bit before they
do it. Otherwise it uses the bandwidth and wait states for 8 bit access.
That may happen when you do a single byte write to memory, I'm not sure.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me