Date: Sun, 11 Feb 2001 15:38:00 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Matt Dillon <dillon@earth.backplane.com> Cc: Warner Losh <imp@harmony.village.org>, Jesper Skriver <jesper@skriver.dk>, Robert <robert@chalmers.com.au>, freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: uh oh - after 4 -> 4.2 cvsup, no keyboard. any ideas? Message-ID: <200102110638.PAA07364@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Sat, 10 Feb 2001 22:19:49 PST." <200102110619.f1B6Jn830124@earth.backplane.com> References: <20010204112503.E71706@skriver.dk> <EJEPLCEELLLLAMPNEJMHIECHCLAA.robert@chalmers.com.au> <200102110424.f1B4OVW18984@harmony.village.org> <200102110446.f1B4ksR29654@earth.backplane.com> <200102110525.OAA06084@zodiac.mech.utsunomiya-u.ac.jp> <200102110549.f1B5n8A29927@earth.backplane.com> <200102110616.PAA07027@zodiac.mech.utsunomiya-u.ac.jp> <200102110619.f1B6Jn830124@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>:The flags 0x1 was added to the AT keyboard driver when the USB >:support was added to GENERIC by default in -CURRENT (GENERIC >:rev 1.255) and in -STABLE (GENERIC rev 1.246.2.5). (I don't recall >:many complaints at that time...) >: >:We need to develop consensus on this. >: >:Kazu > > What if we simply created an API to overload the syscons input device? > That is, allow any device driver to install a syscons input device. The > most recent device driver to do so is the one that gets called. If it > deinstalls itself, prior device drivers take back over. We wouldn't > worry about allowing input from two sources at the same time... one would > simply override the other with the other going into the bit bucket. > > It looks like it would be fairly easy to do in the code. It would be > a small, simple structure managed in a linked list. > > Then *all* keyboard device drivers would be allowed to probe independantly > from each other. We simply probe the AT keyboard device first. It will > nominally succeed. Then later on we probe the USB keyboard and if it > exists it simply overloads the AT device (AT key strokes start going into > the bit bucket). If the USB keyboard is removed, it removes its > overloading and the AT keyboard works again. > > -Matt There ALREADY exists a mechanism to tell syscons which keyboard to use. See kbdcontrol -k device. All we should do now is to add this to /etc/usbd.conf... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102110638.PAA07364>