Summary: | Adding quirk entry for some (Acer C720P Chromebook) firmware in keyboard module | ||
---|---|---|---|
Product: | Base System | Reporter: | pitwuu |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Some People | CC: | gonzo, grembo |
Priority: | --- | Keywords: | easy, feature, needs-patch, needs-qa, patch |
Version: | CURRENT | Flags: | koobs:
mfc-stable10?
koobs: mfc-stable9? |
Hardware: | Any | ||
OS: | Any |
Description
pitwuu
2015-11-14 18:39:39 UTC
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. |