From owner-freebsd-alpha Mon Oct 30 13: 8:16 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9610537B4D7; Mon, 30 Oct 2000 13:08:09 -0800 (PST) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9UL7Rf81062; Mon, 30 Oct 2000 13:07:27 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 30 Oct 2000 13:08:29 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: minor patchlet for others to try .. Cc: alpha@FreeBSD.org, "David O'Brien" , Bernd Walter Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Oct-00 Matthew Jacob wrote: > > Same for me. This little patchlet really doesn't cover the EB164 PC164 > variants, but is mostly for me to see whether it *breaks* other folks. > > Formally speaking, if I can be so bold to say as much about code I didn't > design and probably don't understand, as each interrupt comes in and a thread > is scheduled to run but isn't running, there is an attempt to disable the > interrupt source in h/w (not at the device but at h/w in the system that > allows the transmission of interrupts). PCI interrupts were/are being handled > by each alpha's platform PCI code. > > The isa code wasn't setting up enable/disable vectors. I want to add them and > see if breaks people. The semantics should be the same as the PCI stuff- and, > haha, even close the x86 code that this design seems to come from. Grrrr. So ISA interrupts are level-triggered on the 164? Ugh.. > -matt -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message