Re: vsbus doc?

Hello,

correct Johnny, the "vsbus" was just to hang devices on which needed the 
vaxstation properties (interrupt registers, DMA, ...). 
Uba/mba/bi/sbi/vsbus/... are just all handled as buses with different 
properties.

-- R

Den 2026-04-09 kl. 11:00, skrev Johnny Billquist:
> Ragge can preobably make a better comment on this, but my 
> recollection/understanding is that "vsbus" is just an artificial name 
> since you need some kind of bus to hang all the drivers off, and you 
> need to call it something.
>
> Not sure how much, if anything actual physical represents this. But it 
> holds the I/O space, and manages DMA.
>
> If this answer makes any sense, I don't know. :-)
>
>   Johnny
>
> On 08/04/2026 17.18, Mouse wrote:
>> I'm finding myself wanting to backport support for the 3100/80 from 5.2
>> and/or 4.0.1 to 1.4T.
>>
>> To some extent, I can just copy code.  But I'd like to understand it,
>> if only to make sure I get it integrated correctly.
>>
>> The major piece I'm aware of at the moment that I don't understand is
>> the hardware backing (what 4.0.1 and 5.2 call) vsbus.  Clearly
>> _someone_ understood it at some point, or the code wouldn't exist.  So
>> what I'm asking is, does anyone know of any documentation on that
>> hardware, documentation suitable for someone writing OS-level code for
>> it?
>>
>> I haven't gone searching because I don't know what to search for.  I've
>> done a little searching for 3100/80 stuff, but the false positives
>> always flood the search results to the point of uselessness, so I
>> clearly haven't found the right search terms.
>>
>> /~\ The ASCII                  Mouse
>> \ / Ribbon Campaign
>>   X  Against HTML        [email protected]
>> / \ Email!         7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>