??? 09/09/04 14:08 Read: times |
#77130 - RE: Proposal: Internal Data Bus Responding to: ???'s previous message |
1) Looks like i didn't understand the co-processor division, very well. Thought i/o co-proc was "link i/o" such as, keyboard, mice, paddles, serial, parallel, net... That too. I suspect mass storage can be handled by that same 8052 though. If not it could be broken out into a fourth slave. I was thinking of the case where video and audio might play off the disk. With interrupts you could compensate for the lack of DMA by using buffer interrupts to simply route data to Video/Audio. Wow, looking to play movies and MP3s off this thing, are you? :) But you raise a good point in terms of thinking ahead. You're right, we need to keep that approach in mind. A less founded argument could be coded into a question; what else would you be doing with the interrupt? Not much. And you're right, the I/O is going to have to have some interrupt ability. Otherwise we're going to have to constantly poll for mouse movement, keypresses, network traffic, etc. At the very least the I/O slave has to be able to issue an interrupt when it has some data to give to the master. I wouldn't think video would need to interrupt the master since it is output only. I doubt the audio 8052 would need to interrupt the master--unless we're considering a soundcard-like "Audio In" functionality to digitize incoming audio?? Regards, Craig Steiner |