26 Mar
2019
26 Mar
'19
8:31 p.m.
On Tue, Mar 26, 2019 at 5:10 PM Bill Gunshannon via cctalk
<cctalk at classiccmp.org> wrote:
On 3/26/19 7:54 PM, Dennis Boone via cctalk wrote:
I didn't set it. It came that way in the 2.11 distro.
It apparently picks a free vector when it is activated as
demonstrated by the listing provided by init.
tms 0 csr 164334 vector 774 vectorset attached
bill
When in doubt, Use the Source.
src\sys\autoconfig\do_config.c
expect_intr(dp)
DTAB *dp;
{
HAND *hp;
register int addr = dp->dt_vector;
/*
* A vector of 0 has special meaning for devices which support programmable
* (settable) vectors. If a xxVec() entry point is present in the driver and
* /etc/dtab has a value of 0 for the vector then 'autoconfig' will allocate
* one by calling the kernel routine 'nextiv'.
Mine has
two entries:
tms 0 174500 260 5 tmsintr #
tmscp driver
tms 1 164334 0 5 tmsintr # tmscp driver
You set the vector on the second one to zero. Should it be
something else?
De