Date: Sat, 21 Jan 2012 14:11:54 +0900 (JST) From: <aconnolly08@yahoo.co.jp> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: atkbc not loaded with ACPI enabled in 9.0 Message-ID: <639642.41300.qm@web100410.mail.kks.yahoo.co.jp> In-Reply-To: <201201171015.32364.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- On Wed, 2012/1/18, John Baldwin <jhb@freebsd.org> wrote:
On Friday, January 13, 2012 10:27:13 pm aconnolly08@yahoo.co.jp wrote:
> Please try this patch:
>=20
> Index: sys/dev/atkbdc/atkbdc_isa.c
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- atkbdc_isa.c (revision 230009)
> +++ atkbdc_isa.c (working copy)
> @@ -87,6 +87,7 @@ static driver_t atkbdc_isa_driver =3D {
> =20
> static struct isa_pnp_id atkbdc_ids[] =3D {
> { 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
> + { 0x0320d041, "Keyboard controller (i8042)" }, /* PNP0320 */
> { 0 }
> };
> =20
>=20
> --=20
> John Baldwin
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org
> John,
> Thanks for your help, but that patch doesn't appear to address the proble=
m.=20
I edited the atkbdc_isa.c file as you instructed, rebuilt and installed my=
=20
kernel, but my integrated keyboard remains unresponsive with ACPI enabled.
> Here's the new output of dmesg -a http://pastebin.com/h6ahmD2ddevinfo -ur=
=20
http://pastebin.com/sdNcNEJUdevinfo -vr http://pastebin.com/P2yqQBLY
> Perhaps I was supposed to remove PNP0303 support?
No, the goal was to get atkbdc to try to attach to PNP0320 devices since th=
ose=20
have your keyboard I/O ports. Can you add some printfs to atkbdc_isa_probe=
()=20
to see how many times it is getting past the ID check, and how far along it=
=20
gets in each cases (i.e. which failure case causes the probe routine to ret=
urn=20
an error)?
--=20
John Baldwin
John,
I added some printfs to the isa_probe() function to see how far it was gett=
ing. The function is called many times as you can see in the dmesg, but mos=
tly it exits at the PnP ID check with ENXIO.
At one point it gets further, but still exits with ENXIO when port0 is foun=
d to be NULL.
Any suggestions for further investigation?
edited function http://pastebin.com/uUsVLiz2
dmesg -a http://pastebin.com/kDtC9gvM
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?639642.41300.qm>