01-28-2020, 11:52 AM
(01-28-2020, 03:28 AM)as400 Wrote: @jackhumbert - I have updated ANSI keyboard before (with oem files). Can I just run last step of your instructions - ./updater flash-kb-revised ansi ?
Yeap! `sudo` should be needed I think.
(01-28-2020, 02:05 AM)ssfrfr@ Wrote:(01-22-2020, 03:18 PM)jackhumbert Wrote: If you have any bug reports or suggestions for other features, feel free to open an issue/PR in the repo, or discuss things here!
I'd be happy to test out a dvorak mapping, or even generate one if needed -- I recently built a keyboard, and having hardware dvorak is really nice.
The documentation says the .asm files aren't -- does that apply to the .a51 files?
Having a comprehensive way of remapping keys would be awesome, particularly if it could be as easy as Soarer's converter for simple mods, but with the ability to do more ornate mappings (Fn-key, maybe even layers) as well.
I've started converting these assembly-ish files into c code and keymaps that can actually be compiled with sdcc: https://github.com/jackhumbert/pinebook-...c/keymaps/ - hopefully the format I have here makes sense. This branch isn't thoroughly tested yet, so please be careful when thinking about flashing from `c_source` (`master` is stable). I've only created ANSI versions for now since that's all I'm able to personally test at this time. Theoretically we can create an ISO mapping using the ANSI .hex file as a base (as opposed to the ISO one), but I'm not sure if there's any other differences yet.
it'd be nice to have the updater able to flash arbitrary .hex files instead of needing to rename and recompile each time. Ideally we can have a bunch of keymaps in here for people to flash/try out based on what they want.