Date: Sat, 07 Jul 2012 08:25:55 +0900 From: Kaho Toshikazu <vinwa@elam.kais.kyoto-u.ac.jp> To: John Baldwin <jhb@freebsd.org> Cc: Matthias Apitz <guru@unixarea.de>, freebsd-current@freebsd.org, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: no keyboard after booting r235646 in laptop FS Amilo D 7830 Message-ID: <14213.1341617155@elam.kais.kyoto-u.ac.jp> In-Reply-To: Your message of "Fri, 06 Jul 2012 08:13:39 -0400" References: <201206301349.58930.erich@alogreentechnologies.com> <201207050739.18457.jhb@freebsd.org> <1162.1341543847@elam.kais.kyoto-u.ac.jp> <201207060813.39867.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, John Baldwin <jhb@freebsd.org> wrote: > Almost all systems use one of the IDs we do support as a _CID if not a _HID. > In fact, in this case it likely seems to be a BIOS bug as it used the same > value for the _CID and _HID. I suspect it is supposed to be using 0303 as its > _CID. I don't think the BIOS should say PNP0303 as a keyboard _CID. Using _CID may help some systems, but it may not be helpful for many systems having keyboard probe problem. I think it's a specification bug made by Microsoft, same devices connected different type devices should not have different ID but same ID. > > http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/pnp_legacy.doc > > Note that 030B is listed as reserved in this table, and not a valid keyboard > device. Yes, it's a invalid type, but reserved as a keyborad. I don't know why the BIOS builder puts PNP030B as a keyboard, but it seems to be not a bug. People with this problem can override AML code, but I don't think it is a bad idea adding other IDs to the list for probing. -- kaho@elam.kais.kyoto-u.ac.jp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14213.1341617155>