Date: Mon, 30 Oct 2000 13:08:29 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Matthew Jacob <mjacob@feral.com> Cc: alpha@FreeBSD.org, "David O'Brien" <obrien@FreeBSD.org>, Bernd Walter <ticso@cicely8.cicely.de> Subject: Re: minor patchlet for others to try .. Message-ID: <XFMail.001030130829.jhb@FreeBSD.org> In-Reply-To: <Pine.LNX.4.21.0010300937260.14689-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001030130829.jhb>