Date: Thu, 24 Dec 1998 14:32:56 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith <mike@smith.net.au> Cc: des@flood.ping.uio.no, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: future of syscons Message-ID: <199812240533.OAA25068@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Wed, 23 Dec 1998 19:51:15 PST." <199812240351.TAA00736@dingo.cdrom.com> References: <199812240351.TAA00736@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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 thu >s >> 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. I think it's dangerous to take both interrupts "automatically" when the keyboard controller is detected. 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. I expect all these chores will be solved by decent config(8) and bus code...Then, we should do everything right :-) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812240533.OAA25068>