30 Jul
2007
30 Jul
'07
12:52 p.m.
One other thing. Ususally one doesn't see this one
but on a machine I
put together, using a different processor, on one command I was
able to beet the busy response of the controller chip. It was on only
one command but I don't recall which command.
If the PC is running the bus faster than the 765 is clocking, one can
be too quick.
I recall putting a short delay to make sure the status read was coorrect.
I know it was this because I did an experiment that I'd read it twice.
The second read was OK but not the first.
Thanks - I hadn't thought about that, and I'll look into it. Funny thing
about PCs - slower CPU (even significantly slower) doesn't necessarily mean
slower time between I/O accesses... This could be a factor.
Dave
--
dave06a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.classiccmp.org/dunfield/index.html