From owner-freebsd-current Wed Dec 23 19:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01330 for freebsd-current-outgoing; Wed, 23 Dec 1998 19:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01325 for ; Wed, 23 Dec 1998 19:55:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA00736; Wed, 23 Dec 1998 19:51:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812240351.TAA00736@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: mike@smith.net.au, des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Thu, 24 Dec 1998 12:44:26 +0900." <199812240344.MAA22380@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 19:51:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > msmith>> controller kbdc0 at isa? port IO_KBD tty > msmith>> device atkbd0 at isa? tty flags xxxx > msmith>> device psm0 at isa? tty flags yyy > msmith> > msmith>Just to note that ultimately you won't specify the 'tty' mask here, but > msmith>rather in the interrupt connection function, so: > msmith> > msmith>controller atkbdc0 at isa? port IO_KBD > msmith>device atkbd0 at kbdc? > msmith>device psm0 at kbdc? ... > msmith>Also, since the atkbd and psm device interrupt handlers can only be > msmith>called from the atkbdc driver, they don't register interrupts and thus > msmith>don't have/need masks. > > There is a compromise here too. In i386, if atkbdc wants to have TWO > interrupt handlers, it has to call register_intr() directly (and make > sure that there won't be conflicts), rather than letting > isa_configure() to do the deed, because isa_configure() can assign > only one interrupt to a device. Am I wrong? 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. -- \\ 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