I'm moving a static device driver from Digital Unix 3.2D to Digital
Unix 4.0, and I'm hoping someone has some more information on how to
debug drivers in this environment.
Currently, I have a driver that I can load (using "sysconfig -c myri")
into a running Digital Unix 4.0 kernel. I've placed printf()'s in the
driver code, and from those it's clear that the PCI device is
recognized and configured. Both the probe and attach() routines are
called.
Neither routine really does anything - the probe records the
controller information to be used later when an open call is made, and
then return a "1" allegedly indicating success. Attach doesn't
anything but return.
Immediately following having the attach routine called, the system
locks up complete, and the only thing I can do is reset the machine.
I have enabled the PCI_Developer_Debug option, but all that does is
show the PCI subsystem identifying the vendor & device ID on the
cards.
To me, it seems like some step in the autoconfiguration process is
barfing after successfully identifying the device. I can't really make
much further progress w/o some way of determining what the autoconfig
system is trying to do after it calls attach.
The online reference manuals are, to say the least, a wee bit less
than helpful on this topic, and our DU4.0 source distribution hasn't
shown up yet.
I'm hoping some other device hacker for DU4.0 might have some guidence
to offer.
Dirk Grunwald Assoc. Prof, Univ. of Colorado at Boulder
Received on Wed Jul 31 1996 - 01:57:26 NZST