>You've hit most of the important signals. One I'd add, however, is a data
>bus disable, and perhaps an address bus disable as well. This would allow a
>front panel or other bus mastering device to steal cycles under certain
>circumstances.
Why wouldn't BUS REQUEST work?
>What would you do with the HALT signal, and how would you implement it?
WAIT sould act as a "pause and hold the bus in it's current condition"
signal. Halt should mean "Stop what you are doing, release the control of
the bus and wait until the HALT signal is removed". IMHO
>There's some debate about how one should signal the beginning of a new bus
>cycle. This should be at the earliest moment at which addresses are
>stable.
I guess the RD/WR signals should be seperate and only applied AFTER all
signals on the bus are stable.
----------------------------------------
Tired of Micro$oft???
Move up to a REAL OS...
######__ __ ____ __ __ _ __ #
#####/ / / / / __ | / / / / | |/ /##
####/ / / / / / / / / / / / | /###
###/ /__ / / / / / / / /_/ / / |####
##/____/ /_/ /_/ /_/ /_____/ /_/|_|####
# ######
("LINUX" for those of you
without fixed-width fonts)
----------------------------------------
Be a Slacker!
http://www.slackware.com
Slackware Mailing List:
http://www.digitalslackers.net/linux/list.html
Received on Tue Mar 30 1999 - 12:48:34 BST