Support for Alternative Layouts
This is a summary of how alternative layouts have been supported by kits such as Colevrak and Homing. It is not a discussion of alt layout performance and development, but if that interests you I highly recommend starting with Pascal Getreuer’s A guide to alt keyboard layouts (why, how, which one?). It’s a concise and comprehensive overview with links to some great sites that go deeper. He also has a separate Links about keyboards page. The Keyboard layouts doc he recommends explains layout goals and metrics in detail, summarizing the alt layouts discussed here as well as more than one hundred others. Sculpted-profile The majority of custom keycap sets are sculpted-profile (Cherry, SA, MT3, KAT, etc. - more on profiles generally here) so let’s start there. Because each row has a unique keycap shape, alt layouts require a unique keycap for each legend that moves off its QWERTY row. At first there were two The Dvorak layout was patented in 1936 by August Dvorak & William L....
Apr 23, 2024
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2014 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to dfu-util@lists.gnumonks.org
Cannot open DFU device 0a5c:21e6 Found DFU: [1c11:b007] ver=0000, devnum=23, cfg=1, intf=0, alt=0, name="Kiibohd DFU", serial="mk20dx128vlf5" ============================================
using win8.1. what does "Cannot open DFU device 0a5c:21e6" mean? can I ignore this message and flash without running into problems like the other guy? In any case, I ended up flashing through linux just in case.
Found DFU: [1c11:b007] ver=0000, devnum=21, cfg=1, intf=0, alt=0, name="Kiibohd DFU", serial="mk20dx128vlf5"
Return Code: 0 dfu-util 0.8
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2014 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to dfu-util@lists.gnumonks.org
Match vendor ID from file: 1c11 Match product ID from file: b007
Opening DFU capable USB device... ID 1c11:b007 Run-time device DFU version 0110 Claiming USB DFU Interface... Setting Alternate Setting #0 ... Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing DFU mode device DFU version 0110 Device returned transfer size 1024 Copying data from PC to DFU device
Download [=========================] 100% 32380 bytes Download done. state(7) = dfuMANIFEST, status(0) = No error condition is present
unable to read DFU status after completion
Return Code: 0
1) Do you have any other computers to try flashing with? 2) Try running kii-dfu with administrator privileges 3) Download http://dfu-util.sourceforge.net/releases/dfu-util-0.9-win64.zip, extract, copy kiibohd.dfu.bin to that directory, open up a command prompt (administrator mode), cd to the dfu-util.exe directory, dfu-util -l (this will list your keyboard to see if it's in flash mode), dfu-util -D kiibohd.dfu.bin (this will flash the keyboard).
The keyboard does not respond to any attempt to interact with it. The operating system does not recognize its presence. I've tried multiple PCs, multiple cables, and multiple USB ports. Everything is pointing to the keyboard itself as the source of the problem.
I'd really like to take a look at the keyboard personally. Would you mind shipping the keyboard to me? It shouldn't take me more than a day to solder on a new MCU (if that's what's actually dead). Then I'll ship it back to you.
It's quite a bit of work sadly. The unfortunate answer is that Apple keyboards don't follow the HID spec. They use a bunch of cludges to add things like the FN key (which does not exist in the HID spec, but they still pass it on to the OS). Since this is boot mode (early startup), very likely it would break support for some BIOSs. As we know Apple doesn't care about compatibility with anyone but whatever their latest computer is (they are terrible for backward compat on even their own hardware).
(also, any Apple devs working on HID reading this, don't worry, all keyboard manufacturers hate you; it's by far the worst platform to develop hardware for)
Anyways, enough venting. I think it still might be possible to make it work. Please file a github issue here -> https://github.com/kiibohd/controller/issues I have an apple keyboard kicking around so I can at least check out what kind of descriptors it's using.
I'm also going to ping hasu and some other keyboard firmware devs to see if they've looked into this.