From owner-freebsd-hackers Mon Sep 16 16:05:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA18650 for hackers-outgoing; Mon, 16 Sep 1996 16:05:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA18644 for ; Mon, 16 Sep 1996 16:05:03 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA00146; Tue, 17 Sep 1996 09:04:29 +1000 Date: Tue, 17 Sep 1996 09:04:29 +1000 From: Bruce Evans Message-Id: <199609162304.JAA00146@godzilla.zeta.org.au> To: bde@zeta.org.au, SimsS@Infi.Net Subject: Re: Problem with sio0 Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I've stuffed a couple of diagnostic printf's into sio.c and have = >empirically proven that the probe on a Compaq LTE/Elite returns 1's in = >failures[5] and failures[8]. That is to say, with isa_irq_pending. This says that the interrupt being tested for arrives late (after it is masked in the UART :-(). >A couple more minutes under the microscope shows that the sio0 probe is = >being called with IRQ=3D0x10, even though the kernel's configed as IRQ4 = >(and verified by a boot -c. FWIW: the sio1 probe is called with IRQ = >0x08. I'm not sure what 3D0x10 is. IRQ4 _is_ 0x10 (see /usr/src/sys/i386/isa/isa.h) so 0x10 is the default. failures[8] says that probing the port probabky caused an IRQ4, so IRQ4 is probably correct. >So.... Not knowing ANYTHING, I offer the following question: how / = >where does the *dev structure get filled in before being passed into = >sioprobe()? It appears that that's where the failure starts, but I'm in = >*way* over my head.... The structure is initialized at compile time and not changed unless you use -c. I don't think the problem is there. Bruce