qmk_firmware VS WSL2-Linux-Kernel

Separate wireless controller, see the glue code at [0]

[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...

If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].

[0] https://qmk.fm/

I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.

Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999

Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.

UPDATE: after fluffing around a little bit, I have manged to fix this code: https://github.com/qmk/qmk_firmware/blob/master/keyboards/lily58/keymaps/bongocat_wpm_responsive/keymap.c and flash it successfully - it seems not to be working correctly as the cat is only hanging there and does not respond to the wmp count. If anybody spots anything wrong in the code please let me know!(C is not my language but I am a programmer, I am gonna get at it again over the weekend if I have time left)

For Seniply I've found this implementation for a_dux keyboard: QMK

By the way, Microsoft publishes the WSL kernel source, under GPL, as they must: https://github.com/microsoft/WSL2-Linux-Kernel

From here on out it gets a bit hazy. For kernel builds you will have to use the Microsoft Linux Kernel (don't laugh, it's actually a thing). The USBIPD project walks through a WSL kernel build, so you can use that as a guide of sorts. Once you've done everything you need with the disk, the Gentoo project shows how to import it, but if you already have the VHDX file, I think the import-in-place option may be simpler. Take care in CH2 when making the filesystem. I'm not sure if WSL want's only one ext4 partition or if it walks the disk looking for root. There may be some .wslconfig settings for this, my first guess would be kernelCommandLine.

This was true for WSL1, but WSL2 does contain a Linux kernel. The source code for it is available at:

https://github.com/microsoft/WSL2-Linux-Kernel

git clone --branch mytag0.1 --depth 1 https://github.com/microsoft/WSL2-Linux-Kernel use tag for your version

But if you need a custom kernel then build it by taking Microsoft's kernel config as your base and then set the following up accordingly in your %USERPROFILE%\.wslconfig file:

It uses a customized version of the Linux kernel (repo) that integrates with the host Windows OS. You can build any distro on top of that kernel, as people have done with (of course) Arch. The distro isn't any less "real" than a distro that it run on QEMU (and with a level 1 hypervisor, all systems that uses one are technically virtualized already).

I recompiled the kernel using sources from https://github.com/microsoft/WSL2-Linux-Kernel with experimental genpatches applied.

KERNVER=$(uname -r | cut -f 1 -d'-') git clone --branch linux-msft-$KERNVER --depth 1 https://github.com/microsoft/WSL2-Linux-Kernel.git ~/kern-$KERNVER zcat /proc/config.gz > ~/kern-$KERNVER/.config make -C ~/kern-$KERNVER -j 4 make -C ~/kern-$KERNVER -j 4 modules_install ln -s /lib/modules/$KERNVER-microsoft-standard-WSL2+ /lib/modules/$KERNVER-microsoft-standard-WSL2