Hello,
Sorry for the late reply, I've been unable to answer earlier.
On Fri, May 10, 2019, 17:31 Simon Newton simon@simonnewton.com wrote:
Strangely, the solution to this problem is to tell coreboot to *not* handle the PS2 init and leave it to the payload.
using value
CONFIG_DRVIER_PS2_KEYBOARD is not set
results in the ps2 keyboard working fine when the payload init's it.
Yes, the keyboard only needs to be initialized once. Only if the payload does not do PS/2 init then coreboot should do it. I've never needed to tell coreboot to init PS/2 on my boards when using SeaBIOS because of that.
I checked devicetree and the mappings look correct from the ioport dump
and superio dump, so unsure of why the coreboot init would cause this problem, but the solution seems to be "let the payload handle it"
Cheers Simon
Best regards,
Angel Pons