Date: Mon, 9 Jul 2012 11:53:25 -0400 From: John Baldwin <jhb@freebsd.org> To: Kaho Toshikazu <vinwa@elam.kais.kyoto-u.ac.jp> 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: <201207091153.25092.jhb@freebsd.org> In-Reply-To: <14213.1341617155@elam.kais.kyoto-u.ac.jp> References: <201206301349.58930.erich@alogreentechnologies.com> <201207060813.39867.jhb@freebsd.org> <14213.1341617155@elam.kais.kyoto-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, July 06, 2012 7:25:55 pm Kaho Toshikazu wrote: > 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. Well, my point is that having a _HID and _CID with the same ID is pointless. It really does look like a typo in the BIOS source. > 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. Adding IDs is cheap, so I'm fine with doing so. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207091153.25092.jhb>