On 02/04/2019 15:04, Stephen Borrill wrote:
Well I've figured out what is going on. For some reason your keyboard is generating different scan codes to the one expected by the NetBSD driver. NetBSD seems to be expecting AT scan code set 1.On Mon, 1 Apr 2019, Mike Pumford wrote:The patch doesn't seem to help. I did try bypassing the RISC OS boot sequence just in case I had some odd module loaded that did something strange.On 28/03/2019 09:43, Stephen Borrill wrote:
Using z as an example: In Set 1: down: 0x2c up: 0xac In Set 2: down: 0x1a 0xf0 up: 0x1aIf we look up 0x1a in set 1 that maps to [ so this explains the [[ you get when you type a z. I checked the other examples you gave and they all lined up this way. Just need to work out why there is a disconnect between hardware and software (and why it happens on your system and not mine ).
I'll keep digging to see if I can come up with a patch. Mike