[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: About support for rtVAX300
Roger Ivie wrote:
> On Sun, 13 Jan 2013, Holm Tiffe wrote:
> >I found an vector specification for the SCN2681 for 0x2c0 in the manual,
> >how this is related with the IPL14? Can please someone try to enlighten me?
> I believe those are just what VAXeln expects from rtVAX 300 hardware. If
> the design needs console interrupts, VAXeln expects those interrupts to
> occur at IPL 14 with a vector of 0x2c0.
> The rtVAX 300 does not include hardware to generate the console vector. If
> the design needs console interrupts, they have to be generated by external
> hardware. There's an example of such hardware in chapter 6.
> roger ivie
Good. I don't tried to check where may the INTRN line from The UART is
connected to, I hope that the neccessary hardware is one of the four PLDs
on that board. I'll see later if the UART is able to generate interrupts at
So ist should be ok to use that:
scb_vecalloc(0x2c0, (void (*)(void *)) scnintr, sc,
for the SCN2681 (if the hardware supports this)?
(I'm not at that point where the scn driver should run over Interrupts at
How about the sgec?
Can I freely decide which vector is to be used?
As far as I've seen this vector is written to the NIC cr0 and
with the same mechanism as above to the vector table.
Since the NIC is doing nothing, is it possible that INTs aren't
activated at all in the moment?
(Remeber, there are some memory Addresses with some incontrol and intmask
like names on the ka650, may be I have to look at this?)
Since there seems to be no external intmask logic on the rtVAX (at least
there is nothing documented), enabling the IPLs with MFPR/MTPR should be
enough already? (splx?)
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
Main Index |
Thread Index |