Thanks; seems the chromebook kernel keyboard driver isn't sending scan codes along, but the actual key codes seem correct (F1 to F10) *if* they are actually F keys. If they are supposed to do something else, then the kernel needs to be fixed first to report proper scan codes.
Thanks; seems the chromebook kernel keyboard driver isn't sending scan codes along, but the actual key codes seem correct (F1 to F10) *if* they are actually F keys. If they are supposed to do something else, then the kernel needs to be fixed first to report proper scan codes.