From: bray@wcuvax1.wcu.edu (Jim Bray) Subject: More on Elite16 problem(solved: irq) and busmouse.c suggestion Date: Mon, 7 Dec 1992 03:09:55 GMT
I now have everything working more or less on my 486/EISA/SCSI box.
My problem with the Elite was that it was using irq2, which works for
my sysV thing. I approached the infinite loop as a kernel bug, and eventually
solved it by finally grepping my way to Space.c and finding the default
configuration. Now that the net is up, I looked at README.tcp and lxnet.faq
and found all these wonderful answers.
Does anyone out there have an online Elite16 hardware reference? A kind
soul at 3com sent me an excellent reference on their 3c509 board. I'd like
to make the driver autoconfigure better if possible. One can apparently tell
the 3c509 what irq to use. Much better than hard-coding it.
I discovered at least three devices that use irq 5: the busmouse,
the Seagate st01/st02, and the worthy wd8013. For yucks I reset my
board to irq 5 to see what would happen. The board came up fine, and
the mouse died. The busmouse code doesn't allocate its irq until you
open it. Perhaps there is a good reason for that, but I changed it in my
version. Here are the diffs (from 0.98.6):
elentari[0]diff -b busmouse.c /usr/local/linux/linux/kernel/chr_drv/busmouse.c
65c65
< /* free_irq(MOUSE_IRQ);*/