New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use KC_LANG1 & KC_LANG2 key #312

Closed
vvakame opened this Issue May 7, 2016 · 20 comments

Comments

Projects
None yet
5 participants
@vvakame
Contributor

vvakame commented May 7, 2016

Hi, I'm enjoying ErgoDox EZ!

I want to use KC_LANG1 & KC_LANG2 Key that is important feature for japanese user.
KC_LANG1 is switch to english input mode and KC_LANG2 is switch to japanese input mode key.
Here is my keymap.c https://github.com/vvakame/qmk_firmware/blob/0e1bb350ab3efc1473b25e256bc648fda0ab2074/keyboard/ergodox_ez/keymaps/vv/keymap.c#L15-L55

I tried CONSOLE_ENABLE=yes and hid_listen.
I added debug log to action_for_key function (keymap_common.c). I got KC_LANG1 response from keyboard. but It was not possible to exhibit the effect. 😿

KC_LANG1&2 is works fine from massdrop settings. https://keyboard-configurator.massdrop.com/ext/ergodox/?referer=XEG9GJ&hash=7c963a9ba9dad9108e4dc854c22aaecd
But qmk_firmware is not.

I'm happy if I get any advice.

@ezuk

This comment has been minimized.

Member

ezuk commented May 12, 2016

@jackhumbert any thoughts on this one?

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 12, 2016

Here are some japanese-specific keycodes from keycode.h - do they do anything for you?

/* Japanese specific */
#define KC_ZKHK KC_GRAVE
#define KC_RO   KC_INT1
#define KC_KANA KC_INT2
#define KC_JYEN KC_INT3
#define KC_JPY  KC_INT3
#define KC_HENK KC_INT4
#define KC_MHEN KC_INT5
@vvakame

This comment has been minimized.

Contributor

vvakame commented May 12, 2016

thank you for advice.
but it is not what I'm looking for..
I think there key is uses for Windows. (I am Mac OS X user)
I'll investigation little by little.


from http://www.usb.org/developers/hidpage/Hut1_12v2.pdf
10 Keyboard/Keypad Page (0x07) and Footnotes 15-20

maybe KC_ZKHK(0x35) means ZenKaku/HanKaku(全角/半角)(Fullwidth/Halfwidth char) input mode toggle key.
http://www.unicode.org/reports/tr11/tr11-15.html

KC_RO(0x87) means switch to input by Romaji(ローマ字) mode.
KC_KANA(0x88) means switch to input by Kana(かな) mode.
https://en.wikipedia.org/wiki/Romanization_of_Japanese

KC_JYEN&KC_JPY(0x88) means Japanese Yen(¥ mark) character.

KC_HENK(0x89) means henkan(変換)(convert) key.
KC_MHEN(0x8A) means mu-henkan(無変換)(no convert) key.

and...
http://www2d.biglobe.ne.jp/~msyk/keyboard/layout/usbkeycode.html
from site write.

Apple Pro Keyboard (JIS-align)
英数 key (switch to english input mode) == Keyboard LANG2 in Usage Name (HID Usage Tables 1.11)
かな カナ key (switch to japanese input mode) == Keyboard LANG1 in Usage Name (HID Usage Tables 1.11)

one more.
I read massdrop generated source code.
and they code use KEY_LANG1(0x90) and KEY_LANG2(0x91). (maybe...)

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 12, 2016

Yeah, it looks like the Massdrop configurator uses 0x90/0x91, so KC_LANG1 and KC_LANG2 should be doing the exact same thing :/ you mentioned that you got a response from these when you used them in QMK - what exactly happened?

This might be a device/vendor ID issue - OS X can be kind of picky about that. It looks like the configurator uses these IDs:

#define VENDOR_ID       0x1d50  // Openmoko, Inc.
#define PRODUCT_ID      0x6028  // ErgoDox ergonomic keyboard

You can modify these in QMK by editing your config.h file.

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 12, 2016

what exactly happened?

I modified this line.
https://github.com/vvakame/qmk_firmware/blob/254503cedab9830cfc192a47d16ed599d6c20e4f/quantum/keymap_common.c#L49-L51

modified code.

    uint16_t keycode = keymap_key_to_keycode(layer, key);

    print("in action_for_key: ");
    phex(keycode);
    print("\n");

    switch (keycode) {

and exec command & get response.

$ ./hid_listen.mac
Waiting for device:.............
Listening:
boogmagic scan: ... done.
Keyboard start.
in action_for_key: 04     # press a key
in action_for_key: 04
in action_for_key: 04
in action_for_key: 1D     # press z key
in action_for_key: 1D
in action_for_key: 1D
in action_for_key: 90     # press KC_LANG1 key
in action_for_key: 90
in action_for_key: 90
in action_for_key: 91     # oress KC_LANG2 key
in action_for_key: 91
in action_for_key: 91

But IME(Input Method Editor) can't get affected.

is this answer intended?


You can modify these in QMK by editing your config.h file.

I tried to modify keyboard/ergodox_ez/config.h.

$ system_profiler SPUSBDataType USB
USB:

    USB 3.0 Bus:

      Host Controller Driver: AppleUSBXHCILPTH
      PCI Device ID: 0x8c31
      PCI Revision ID: 0x0005
      PCI Vendor ID: 0x8086

...omit...

        ErgoDox EZ:

          Product ID: 0x6028
          Vendor ID: 0x1d50
          Version: 0.01
          Speed: Up to 12 Mb/sec
          Manufacturer: ErgoDox EZ
          Location ID: 0x14200000 / 23
          Current Available (mA): 1000
          Current Required (mA): 500
          Extra Operating Current (mA): 0

but I can't get expected result...

@ezuk

This comment has been minimized.

Member

ezuk commented May 12, 2016

@eltang - thank you for your willingness to help, and for wanting to participate!

Before asking question such as this, I ask that you please take the time to fix your own keymap. I'd love to see you apply your considerable expertise to your own issue before helping others, so that you are able to test changes. This is a basic requirement for supporting others -- being able to compile and flash keymaps on your own hardware, so you can evaluate your own suggestions rather than making guesses.

The steps you should follow are clearly outlined here. Please don't hesitate to ask me there if there is anything that you find too difficult or confusing.

For now, I have removed your comment, and will remove similar comments until you are able to find the time to correct your own technical problems. Thanks again!

@vvakame - my apologies. Please don't feel that you need to reply to Eric's vague question, which I have now removed. I will let @jackhumbert take it from here.

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 13, 2016

Hi! I got answer this issue.
but I don't understand why I can solve this issue.
I'll write a report later. please wait.

vvakame added a commit to vvakame/qmk_firmware that referenced this issue May 13, 2016

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 13, 2016

@ezuk @jackhumbert I made commit, it works fine. vvakame@719b866
I can't give explanation... I think maybe OS side driver matter.
I did't change VENDOR_ID and PRODUCT_ID finally.
I can send a pull request. Do you guys think this change is correct?


@mhidaka give support & some comment to me. thanks!

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 13, 2016

Interesting - thanks for sharing! @abcminiuser uses a similarly lower value here (0x65 instead of 0x68 compared to the TMK default of 0xFF) for the keyboard demo in Lufa.

It looks like the 0x68 is used in the configurator's descriptors, which may indicate a 104-key keyboard (0x68 is 104), and 0x65 would be a 101-key one. It's possible that most OSes wouldn't know what to do with the 0xFF (255-key keyboard), which causes this trouble.

I wonder if this is also causing the Mac-related media key problems.

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 13, 2016

Let me test this today, but it's looking good, so if you'd like to create a pull request, that would be awesome :)

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 13, 2016

yay! 👍

I wonder if this is also causing the Mac-related media key problems.

My ErgoDox EZ works fine about KC_MPLY, KC_MNXT, KC_MPRV, KC_VOLU, KC_VOLD, KC_MUTE.

I'll send a pull request. 😉
I'm making & setup Windows environment. please wait.

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 13, 2016

Bad news..

in Windows 10 (Surface Pro 4).
KC_ZKHK is works fine with 0x65 and 0x68.
but KC_RO, KC_KANA, KC_JYEN, KC_JPY, KC_HENK, KC_MHEN is not working with 0x65 and 0x68.

I tried 0x6D but it is not working too. 109(0x6D) keyboard is main stream in Japan+Windows.
0xFF works perfect...

related? https://support.microsoft.com/en-us/kb/927824

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 13, 2016

Ah, interesting. Do those japanese-specific keycodes work in OS X with your changes?

@vvakame

This comment has been minimized.

Contributor

vvakame commented May 13, 2016

Yes!

summary.

in Mac OS X
KC_LANG1 and KC_LANG2 is works fine with 0x65, 0x68 and 0x6D. but 0xFF is not working.
MacBook built-in keyboard does not have KC_ZKHK, KC_RO, KC_KANA, KC_JYEN, KC_JPY, KC_HENK, KC_MHEN key.
vvakame@719b866 works that I expected.

in Windows
KC_ZKHK, KC_RO, KC_KANA, KC_JYEN, KC_JPY, KC_HENK, KC_MHEN is works fine with 0xFF. but 0x68, 0x6D is not working.
109 keyboard does not have KC_LANG1, KC_LANG2.
https://github.com/jackhumbert/qmk_firmware works that japanese user expected. (maybe I think so.)


0x89 is not working Mac and Windows both.


I go to bed. now is 3:00 am in japan.

@jackhumbert

This comment has been minimized.

Member

jackhumbert commented May 13, 2016

Awesome - I'll talk to @ezuk about working on documentation for that, since I'm not sure we wanna commit anything that varies from 0xFF.

Thanks for diving into this!

@zoetrope

This comment has been minimized.

zoetrope commented May 15, 2016

I tried in Ubuntu 16.04.
KC_ZKHK, KC_KANA, KC_JYEN, KC_HENK, KC_MHEN is works fine with 0xFF. but 0x68, 0x6D, 0x89 is not working.

kawaken added a commit to kawaken/qmk_firmware that referenced this issue May 23, 2016

@tmk

This comment has been minimized.

Contributor

tmk commented Jun 5, 2016

Checked HID specification and found description like Logical Min/Max contains signed value. I guess 0xFF means -1, not 255 there and we have to use 16 bit value for Logical Maximum.

Can someone test this patch?

diff --git a/tmk_core/protocol/lufa/descriptor.c b/tmk_core/protocol/lufa/descriptor.c
index c13a81b..bcc4173 100644
--- a/tmk_core/protocol/lufa/descriptor.c
+++ b/tmk_core/protocol/lufa/descriptor.c
@@ -76,7 +76,7 @@ const USB_Descriptor_HIDReport_Datatype_t PROGMEM KeyboardReport[] =
         HID_RI_USAGE_MINIMUM(8, 0x00), /* Reserved (no event indicated) */
         HID_RI_USAGE_MAXIMUM(8, 0xFF), /* Keyboard Application */
         HID_RI_LOGICAL_MINIMUM(8, 0x00),
-        HID_RI_LOGICAL_MAXIMUM(8, 0xFF),
+        HID_RI_LOGICAL_MAXIMUM(16, 0x00FF),
         HID_RI_REPORT_COUNT(8, 0x06),
         HID_RI_REPORT_SIZE(8, 0x08),
         HID_RI_INPUT(8, HID_IOF_DATA | HID_IOF_ARRAY | HID_IOF_ABSOLUTE),
@vvakame

This comment has been minimized.

Contributor

vvakame commented Jun 6, 2016

I'll try your patch tonight! (please ping if I have forgotten...

@vvakame

This comment has been minimized.

Contributor

vvakame commented Jun 7, 2016

I tried it. It works fine in Max OS X!
I'll test on Windows, please wait in a day...

@vvakame

This comment has been minimized.

Contributor

vvakame commented Jun 7, 2016

It works fine in my Mac OS X and Windows 10 environment! 👍

tmk added a commit to tmk/tmk_keyboard that referenced this issue Jun 7, 2016

core: Fix LUFA report descriptor
- Logical Min/Max contains signed value and needs 16 bit to indicate 255
qmk/qmk_firmware#312

@vvakame vvakame closed this Jun 8, 2016

Dhertz added a commit to Dhertz/tmk_keyboard that referenced this issue Jun 8, 2016

core: Fix LUFA report descriptor
- Logical Min/Max contains signed value and needs 16 bit to indicate 255
qmk/qmk_firmware#312

kawaken added a commit to kawaken/qmk_firmware that referenced this issue Jun 9, 2016

Merge branch 'master' into my-keymap
Can't use KC_LANG1 & KC_LANG2 key
qmk#312

に対応した修正を取り込んだ。

kairyu pushed a commit to kairyu/tmk_keyboard that referenced this issue Jun 14, 2016

core: Fix LUFA report descriptor
- Logical Min/Max contains signed value and needs 16 bit to indicate 255
qmk/qmk_firmware#312

tmk added a commit to tmk/tmk_core that referenced this issue Dec 10, 2016

core: Fix LUFA report descriptor
- Logical Min/Max contains signed value and needs 16 bit to indicate 255
qmk/qmk_firmware#312

eltang added a commit to eltang/lufa that referenced this issue Jan 25, 2017

Fix HID_DESCRIPTOR_KEYBOARD()
This will prevent future occurrences of qmk/qmk_firmware#312.

jackhumbert added a commit that referenced this issue Jul 7, 2017

Update Lufa to current build (qmk/lufa) (#1469)
* Replace CDC interface numbers with enums.

* Replace remaining MIDI interface numbers with enums.

* Only issue the REPEAT instruction in the clone programmer if needed to reduce protocol overhead.

* Minor documentation improvements.

* More minor speedups to the AVRISP-MKII clone programmer PDI memory reading code.

* Refactor AVRISP MKII Clone PDI/TPI command constants to simplify the driver code.

* Use non-abbreviated XPROG/PDI/TPI constant names.

* Minor documentation fixes.

* Add Python host test application for the low level GenericHID demo.

* Add new Bulk Vendor device demo application.

* Minor documentation improvements.

* AVRISP-MKII Clone Project PDI/TPI frequency increased from 250KHz to 2MHz as it is now stable.

* Add libusb GenericHID Python test script.

* Fix signature bytes in the DFU class bootloader.

* Minor documentation improvements.

* Add node.js libusb GenericHID test script.

* Minor documentation improvements.

* Increase AVRISP-MKII Clone PDI/TPI handshake to 1ms from 1us for targets with high /RESET line capacitance.

* Fixed MIDI device class driver MIDI_Device_ReceiveEventPacket() for the XMEGA architecture.

* Add Documentation output directories to the .gitignore list.

* Fix incorrect status constants in the AVRISP-MKII Clone project.

* Exclude all host application directories from the Doxygen configuration files.

* Reduce PDI/TPI reset hold period from 1ms to 100us, as the former caused sporadic session issues.

* Use new VERSION_BCD() macro with explicit int arguments to fix edge cases with the previous floating point macro version.

* Fix STK525 and STK526 device support in the Atmel Studio extension.

* Add todo item.

* AVR8: Add option to keep 3.3V regulator enabled

The documentation contains example code[1] on how to restart into the
bootloader. In the process of preparing for the reset, USB is disabled
using “USB_Disable()”. For hardware making use of the AVR8's internal
3.3V regulator that call would also disable the regulator, resetting the
processor immediately rather than setting the boot key and letting the
watchdog reset the processor.

This patch adds a new flag to be given to “USB_Init()” or to be defined
in “USE_STATIC_OPTIONS” telling “USB_Disable()” to keep the regulator
enabled.

On November 1st, 2013 this issue was already mentioned on the mailing
list[2], but no fix came from that discussion.

[1]
<http://www.fourwalledcubicle.com/files/LUFA/Doc/130901/
html/_page__software_bootloader_start.html>

[2]
<https://groups.google.com/d/msg/lufa-support/uwrFpRQpJzU/e9I6UK5jMJQJ>

Signed-off-by: Michael Hanselmann <public@hansmi.ch>

* Minor documentation improvements.

* Fix incorrect Dataflash header file included for the STK525 inside Atmel Studio.

* Update to latest LUFA Atmel Studio integration binary.

* Upgrade Doxygen configuration files to the latest version.

* Minor documentation improvements.

* Update VSIX extension manifest description.

* Minor documentation improvements.

* Add further instructions regarding the modemmanager suckage.

* Minor documentation improvements.

* Update copyrights for 2014.

* Get rid of the redundant ATTR_NEVER_INLINE macro which translated to the same as ATTR_NO_INLINE.

* Minor documentation improvements.

* Minor documentation improvements.

* Update to latest Atmel Studio integration binary.

* Fix broken teensy-ee build rule.

* Update to latest Atmel Studio integration binary.

* Add USB_STRING_DESCRIPTOR and make the Keyboard demo use it.

* Use the new USB_STRING_DESCRIPTOR macro for every string descriptor.

* Add USB_STRING_DESCRIPTOR_ARRAY() macro, update demos where required.

* Minor documentation improvements.

* Fix USB_STRING_DESCRIPTOR() macro reported length to account for the null-terminator.

* Rename all Doxygen.conf file to doxyfile and distribute them in the Atmel Studio extension.

* Fix documentation: jump address for bootloader should be words, not bytes.

* Fix incorrect descriptor length when using USB_STRING_DESCRIPTOR macros.

* Fix ring buffer example.

* Update to latest Atmel Studio integration binary.

* Fix incorrect whitespace.

* Minor typo corrections.

* Add Atmel Studio 6.2 compatibility.

* Update version for the 140302 release.

* Revert version and update documentation after the 140302 release.

* Fix incorrect error codes returned on pip config failure in the host class drivers.

* More fixes for incorrect return types/values.

* Update to latest Atmel Studio integration binary, improve Getting Started page in the manual.

* Fix typos and add new macros for HID keyboard scancodes.

* Upgrade to latest Doxygen.

* Fix LED driver for the Arduino Leonardo board.

* Fixed incorrect XMEGA DFLL reference frequency (thanks to Martin Aakerberg)

* Fix AVRISP-MKII status values to match the published protocol (thanks to Gustavo Souza).

* Fixed spurious 0xFE USART byte sent in the USBtoSerial project when the baud rate is changed (thanks to Carl Kjeldsen).

* Ensure BulkVendor received data is cleared before reading from host.

* Add COMPILER_PATH optional variable to the BUILD build system module.

* Fix possible infinite loop in the control stream write template functions.

* Fix missing report IDs in feature reports

As it is the case for input reports, the ID has to be sent for feature
reports when a device has multiple reports implemented.

Signed-off-by: Bert van Hall <bert.vanhall@avionic-design.de>

* Update documentation for HID report ID fix.

* Add Serial_IsSendReady() and Serial_IsSendComplete() serial driver API functions.

* Only deque from the USBtoSerial's USB->USART buffer when the USART is idle.

* Update bootloader documentation to include execution instructions.

* Minor documentation improvements.

* Fix XMEGA USB prescaler calculation

The USB prescaler calculation for the CLK.USBCTRL register is changed to
give valid results and set the prescaler correctly.

Signed-off-by: Bert van Hall <bert.vanhall@avionic-design.de>

* Minor code style fixes, documentation improvements.

* Fixed USART reception overrun corrupting the internal buffers in the USBtoSerial project.

* Fix Serial_XMEGA.h syntax and define error

* Update Doxygen confiuration files to 1.8.8.

* Remove correct output library file when running make clean in the LUFA build system.

* Patched the LUFA build system to work around a GCC code generation bug in newer toolchains when building for larger FLASH memory devices (thanks to demultiplexer)

* Minor documentation improvements.

* Fix overflow for RNDIS class driver responses when returning the adapter query list (thanks to Peter Mc Shane).

* Minor documentation improvements.

* Minor documentation improvements.

* Add Dual MIDI device class driver demo application.

* Oops: fix incorrect filename in the Dual MIDI device demo.

* add parens around args in MIDI_EVENT macro

* Make twi capitalization match.

* Minor documentation improvements.

* Minor documentation improvements.

* Add board support for the Arduino YUN ATMEGA32U4 coprocessor.

* Oops - include board and LED drivers for the Arduino Yun.

* Add support for the Arduino Micro board, fix other Arduino board LED drivers.

* Add Atmel Studio support for the Arduino Yun and Micro boards.

* Minor documentation improvements.

* Fixed broken AVR8 USART-SPI peripheral driver (thanks to Phil Zakielarz).

* Obsolete the old MACROS and MACROE convenience macros.

* Minor documentation improvements.

* Minor documentation improvements.

* Fixed broken LowLevel Audio Out demo sampling frequency configuration (thanks to Torsten Duwe).

* Update documentation for the 140928 release.

* Add missing MICRO board drivers.

* Update documentation post-140928 release.

* Don't run user application in the bootloader unless a valid app is present (thanks to Alex Kazik).

* The ATPROGRAM LUFA build system module now defaults to the Atmel ICE debuger tool, instead of the Atmel JTAG ICE3.

* Add Leonardo compatibility to most bootloaders, run user application if BOOTRST fuse is set and the last reset cause was not the /RESET pin.

* Fix bootloaders not starting user application if the HWB is grounded during watchdog reset.

* Improve bootloader documentation.

* Revert "Improve bootloader documentation."

Revert commit 2304a73 as it breaks
compilation of the bootloaders.

* Minor documentation improvements to the Mass Storage bootloader.

* Use XPLAIN board by default in the XPLAINBridge project inside Atmel Studio.

* Add board drivers for the Atmel Xplained-MINI kits.

* Upgrade to latest Doxygen.

* Update documentation.

* Update LEDs.h

Changed Led 5 and 4 to be compatible with the official firmware:
https://github.com/arduino/Arduino/blob/master/hardware/arduino/avr/firmwares/atmegaxxu2/arduino-usbserial/Board/LEDs.h#L54-L57

Added TX and RX Led makro

Fixed wrong Led logic: OUT and LOW results in LED on.

* Update Board.h

Added reset lines

* Update BootloaderCDC.c

* Fixed typo in micro board definition in Studio

System was displaying two yun boards in the drop down in ASF Wizard

* Add Progmem Variant to CDC_Device_Send

* ignore HID Bootloader upload tool

* Documentation fixes.

* Minor documentation improvements.

* Minor documentation improvements.

* Add CDC control line state change handlers to the class driver demos, to demonstrate how to read DTR change events.

* Don't fail Doxygen on versions built without various features.

* Patch HID bootloader host app to fix Windows compilation (thanks to Duncan McDonald).

* Fix incorrect XMEGA serial driver stream functions (thanks to William Patterson).

* Update copyrights to 2015 (better late than never).

* Add conflict warning to the AVRISP-MKII Clone project.

* Sourceforge is the devil.

* Fix compilation failure in DualVirtualSerial.c.

A comment on line 236 needed an extra forward slash.

* Minor documentation improvements.

* Add PROGMEM variant data send functions to the CDC host class driver.

* Fixed incorrect signature reported in the CDC/DFU bootloaders for the AT90USB82 (thanks to NicoHood).

* Minor documentation improvements.

* Fixed incorrect comments in DataflashManager.c (thanks to Andrew Milkovich).

* Use 16-bit length for TWI driver packet read/write requests for longer transfers.

* Add DHCP Lease Time to RNDIS Demo

The RNDIS ClassDriver and LowLevel Demo won't work on some Linux
hosts as their DHCP client requires the DHCP Option Lease Time.
Add it to both Demos. Tested on Fedora Linux 22.

* Add ATTR_ALWAYS_INLINE to Endianess helper functions to optimize generated code

Saves 68 Byte on RNDIS LowLevel Demo
Saves 48 Byte on RNDIS ClassDriver Demo

* Minor documentation improvements.

* Update for (in-progress) Atmel Studio 7 support, via new integration DLL and help content fixes.

* I'm getting old. Sadface.

* Update ye-olde copyrights on Atmel Studio integration files.

* Minor documentation improvements.

* Fix Atmel Studio projects not enabling linker relaxations correctly.

* Whitespace fixes.

* Newer AS7 integration binary, with ASF detection fixes and newer image assets.

* Fix dialog typo in the AS7 integration DLL.

* Atmel Studio 7 has a newer AVRISP-MKII firmware payload.

* Update to AS7 integration binary with corrected ASF version detection.

* Fix F1 help resolution from inside Atmel Studio 7 (thanks to Morten Olsen).

* Fix local help content not visible in Atmel Studio 7 (thanks to Morten Olsen).

* Fix AS7 integration, include modified Docbook HV1 transforms.

* Update dfu-programmer command line arguments, old argument names have been changed in newer releases.

* Fixed missing bounds checks and off-by-one in the DFU bootloader signature bytes (thanks to Reuti)

* Update Studio Integration DLL, to include package logging.

* Update Atmel Studio integration binary, to fix broken first-run detection.

* Fix up broken module build tests.

* Commit for the 151115 public release.

* Update documentation and reset version information post-release.

* Fixed incorrect CALLBACK_USB_GetDescriptor() wIndex parameter type (thanks to matlo).

* Fixed broken USE_RAM_DESCRIPTORS compile time option when the FIXED_NUM_CONFIGURATIONS compile time option is not enabled (thanks to Matlo).

* Replace LUFA build system with DMBS.

* Use different jump key than the bootloaders in the documentation.

* Clean up core build system DMBS subclass module.

* Add DMBS; don't Submodule so that people can download complete ZIP/TAR archives.

* Fix C++ builds, XPLAINBridge project.

* Fix HID bootloader CLI app missing va_end() calls.

* Fix additional missing va_end() in the HID bootloader CLI utility.

* Update changelog.

* Fix void pointer arithmetic in the Serial peripheral drivers.

* Fix void pointer arithmetic in the low level RNDIS demo.

*  Fixed low level RNDIS demo incorrectly setting the RNDIS state when a null packet filter was requested.

* Fix additional void pointer arithmetic in the class driver RNDIS demo.

* Minor documentation improvements.

* Minor documentation improvements.

* Added support for the Pololu A-Star Micro board (thanks to Joh Schneider).

* Update copyrights to 2016.

* Add signed Atmel Studio libUSB driver for the AVR-ISP MKII Clone.

* Oops: add missing Pololu Micro board drivers.

* Remove legacy AVRISP-MKII clone compatibility compile options.

* Minor documentation improvements.

* Added AVRDUDE_MEMORY option to the AVRDUDE build system module (thanks to Alex Ferm).

* Only indicate when the left mouse button is pressed in the MouseHostWithParser host demo.

* Fixed invalid endpoint indexes causing memory corruption in device Clear/Set Feature standard requests (thanks to Peter Popovec).

* Added new LUFA_VERSION_RELEASE_TYPE macro to the library version header, to determine release type (thanks to NicoHood).

* Update to latest DMBS version.

* Update to latest version of DMBS.

* Add LUFA DMBS extension modules, use DMBS in project makefiles.

* Don't run the AVRISP-MKII Windows Driver through Doxygen.

* Add missing BOARD_POLOLUMICRO definition.

* Update to DMBS release-20160403 release.

* Fix HID bootloader responding incorrectly to some descriptor requests (thanks to NicoHood).

* Update functions used to write to EEPROM

* Fix outdated URL in the HID bootloader Python host app documentation.

* Update to latest DMBS, fix XPLAINBridge project compilation errors on full tree build.

* Fix USB_SetHIDReportItemInfo() function.

Bits applying loop worked incorrect on large reports. Seems to me like a
copy/paste problem from USB_GetHIDReportItemInfo().

* Minor documentation improvements.

* Use folder-relative output folder in the XPLAINBridge makefile.

* Fix incorrect reference in ASF manifest file.

* Fix HID_DESCRIPTOR_KEYBOARD()

This will prevent future occurrences of #312.

* Minor documentation improvements.

* Revert incorrect Mass Storage bootloader app start address.

* Restrict HID bootloader programming region (thanks to NicoHood).

* Update copyrights for 2017.

* Minor documentation improvements.

* Commit for the 170418 release.

* Update to latest DMBS revision.

* adds QMK board with definable LEDs and matrix scan

* remove old lufa

* add new lufa repo

* update lufa implementation

ma2gedev added a commit to ma2gedev/qmk_firmware that referenced this issue Oct 31, 2017

sini pushed a commit to sini/qmk_firmware that referenced this issue Nov 7, 2017

kgwong added a commit to kgwong/qmk_firmware that referenced this issue Nov 26, 2017

behcet added a commit to behcet/qmk_firmware that referenced this issue Dec 16, 2017

y9v added a commit to y9v/qmk_firmware that referenced this issue Feb 15, 2018

LovesTha pushed a commit to LovesTha/qmk_firmware that referenced this issue Jul 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment