Basically a one-liner to make the keyboard work on my machine (C720p). Has been tested. Update the struct in sys/dev/atkbdc/atkbdc.c:124 static struct atkbdc_quirks quirks[] = { {"coreboot", "Acer", "Peppy", KBDC_QUIRK_KEEP_ACTIVATED | KBDC_QUIRK_IGNORE_PROBE_RESULT | KBDC_QUIRK_RESET_AFTER_PROBE | KBDC_QUIRK_SETLEDS_ON_INIT}, {"coreboot", "Google", "Peppy", KBDC_QUIRK_KEEP_ACTIVATED | KBDC_QUIRK_IGNORE_PROBE_RESULT | KBDC_QUIRK_RESET_AFTER_PROBE | KBDC_QUIRK_SETLEDS_ON_INIT}, {NULL, NULL, NULL, 0} }; Ref: https://lists.freebsd.org/pipermail/svn-src-head/2015-February/068276.html -- Philippe Michaud-Boudreault
CC grembo, who committed the original quirks in r278787 [1] https://svnweb.freebsd.org/changeset/base/278787
This would be a good candidate for MFC
Looks good to me in general (this is pretty much the idea behind those quirks). Question: Is your memory detected properly? The Acer 720 required a quirk boot/i386/libi386/biosmem.c.
hi there, yes, the memory works just fine.
Could you please add the output of kenv and cat /var/run/dmesg.boot to this ticket? (feel free to remove system serial and uuids from the output). Thanks
Hi, would like to bump it. This would fix my issue, could it be pulled in? Basically just adding an entry for 'Google' (which Chromebooks are).
Closing as OBE. The base r307468 marked all Chromebooks as the ones that require keyboard workaround, so there is no need for individual models quirks.