bugeyedcreepy wrote: ↑Sun Dec 03, 2023 3:28 am
Hmmm, perhaps I should look at incorporating something like this into an extended bus design in a way that would allow existing cards and designs to largely work unmolested? That would of course require me to know what I'm doing though - not something that is viable in the short term...
In theory, you could perhaps make a Backplane extender with bus driver ICs included, for driving the "extended" bus.
This would be rather unusual, but perhaps might make some sense in our Minimalist design?
i.e. Retaining the "no buffers needed" for the original 4 otr 5 card Backplane, but introducing buffers for driving an extended system.
But... One catch I can immediately think of is in controlling the enabling of the Data Bus buffers...
Assuming any CPU Card was restricted to only residing on the primary Backplane, then all the Address and Control bus buffers would be outward driving. But the Data bus is bidirectional!
The WR signal is normally used to control the data bus driver direction, which is fine when all peripheral Cards are on the other side of the buffer (as would be the case if the driver ICs were on the CPU Card).
But, if a peripheral Card was also located on the primary Backplane (i.e. inside the buffers), then a read from these Cards would create a bus conflict, with both the peripheral Card and the Backplane extension located bus drivers, both trying to drive the primary Backplane's Data bus at the same time!
Then, if we restricted the primary Backplane to only containing the CPU Card, we would be negating at least 3 card slots from our overall extended Backplane system. Doh!
Hmm.. Sounds like a bad idea. Probably better to design a range of CPU Cards with bus drivers on-board, specifically for supporting an extended Backplane system.
Sorry.. just thinking out loud. LOL