From owner-freebsd-current Mon Dec 28 15:13:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09127 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:13:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09122 for ; Mon, 28 Dec 1998 15:13:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA13485; Mon, 28 Dec 1998 15:10:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812282310.PAA13485@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: Mike Smith , des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Thu, 24 Dec 1998 14:32:56 +0900." <199812240533.OAA25068@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 15:10:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >No, you're right. But there's nothing stopping you have atkbdc do that > >right now; it should never take an interrupt from it's configuration - > >if it detects a kbdc, it should always take both implicitly. > > I think it's dangerous to take both interrupts "automatically" when > the keyboard controller is detected. I don't. We know with absolute certainty which interrupts it will use. > It is true that IRQ 1 is always assigned to the keyboard controller on > the AT motherboard and no device can claim it because IRQ 1 line is > not available in expansion slots. > > The PS/2 mouse interrupt IRQ 12 is another story. IRQ 12 is available > to ISA and PCI bus slots and you can assign it to a device! We > shouldn't make the keyboard controller code to claim IRQ 12 when > either 1) a PS/2 mouse is not detected, or 2) another device is using > or going to use IRQ 12. Sure; by all means disable the interrupt handler if a ps/2 mouse is not found, but it's important to claim the interrupt in the keyboard controller code if one *is* found, or even just expected to be found (eg. attached after bootup). > I expect all these chores will be solved by decent config(8) and bus > code...Then, we should do everything right :-) 8) One step at a time. PCI next. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message