Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: rtVAX300 .. need help..



Holm Tiffe wrote:

> Anders Magnusson wrote:
> 
> > On 01/04/2013 11:21 AM, Mouse wrote:
> > >>Is it using MTPR for console communications?
> > >No.  Its console communication scheme is relatively well-known; between
> > >Holm's efforts and mine, we've found the code in the ROMs which speaks
> > >to the console.  It turns out to be pretty simple, just a little glue
> > >logic in front of a 2681 (or very similar workalike).
> > >
> > Isn't that the same as in the VXT2000?  In that case you could look at 
> > OpenBSD, they have support for the serial chip added.
> > I have never fixed support for the VXT2000 in NetBSD even though I have 
> > one, since I could not get break to work over the serial console so it 
> > became a little bit too tedious to do it :-)
> > 
> > -- Ragge
> 
> The VXT2000 seems to have an SC26C94 Chip which seems to be a descendant
> of the SCN2681, there is a more sophisticated Interrrupt Arbiter
> integrated and the device has four channels.., nevertheless this may be
> useable as a starting point.
> 
> The VXT has it's on vxtbus with only that SC26C94 and the SGEC attached,
> should I do the same on NetBSD (rtVAX300-bus) or should I better use
> something like vsbus?
> 
> Regards,
> 
> Holm
> -- 

I have now created a subdirectory below arch/vax named rtv and try to put
the needed stuff in there.
I've copied the qsc files from OpenBSD, removed some stuff that's not
needed (4 Lines in a chip) and will try to integrate that.
Before I can do that I have to make an modified vsbus (since there are some
other adresses on the rtVAX, uncommon to the rest).
Here I have a problem:

in sys/arch/vax/include/bsbus.h we have this:

/*
 * Some chip addresses and constants, same on all VAXstations.
 */
#define VS_CFGTST       0x20020000      /* config register */
#define VS_REGS         0x20080000      /* Misc CPU internal regs */
#define NI_ADDR         0x20090000      /* Ethernet address */
#define DZ_CSR          0x200a0000      /* DZ11-compatible chip csr */
#define VS_CLOCK        0x200b0000      /* clock chip address */
#define SCA_REGS        0x200c0000      /* disk device addresses */
#define NI_BASE         0x200e0000      /* LANCE CSRs */
#define NI_IOSIZE       (128 * VAX_NBPG)    /* IO address size */

 (since there are some other adresses on the rtVAX, uncommon to the rest).
Here I have a problem:

in sys/arch/vax/include/bsbus.h we have this:

/*
 * Some chip addresses and constants, same on all VAXstations.
 */
#define VS_CFGTST       0x20020000      /* config register */
#define VS_REGS         0x20080000      /* Misc CPU internal regs */
#define NI_ADDR         0x20090000      /* Ethernet address */
#define DZ_CSR          0x200a0000      /* DZ11-compatible chip csr */
#define VS_CLOCK        0x200b0000      /* clock chip address */
#define SCA_REGS        0x200c0000      /* disk device addresses */
#define NI_BASE         0x200e0000      /* LANCE CSRs */
#define NI_IOSIZE       (128 * VAX_NBPG)    /* IO address size */


There is a VS_REGS defined:  Misc CPU Internal regs

On this address in the rtVAX is "User Boot or Diagnostic ROM" located.
I saw that the address gets modified for several CPU Types and that this
stuff is used for DMA...

the rtVAX Manual says that the CPU registers are available trough MTPR
and MFPR, nothing sayd from a mapping somewhere...
There is on page 4-41 metioned that the firmware has shadow copies of many
processor registers.


So what Misc CPU internal Regs are meant here and what should I do?

Regards,

Holm
-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741



Home | Main Index | Thread Index | Old Index