diff options
| author | tmk <tmk@users.noreply.github.com> | 2014-03-06 17:07:50 -0800 |
|---|---|---|
| committer | tmk <tmk@users.noreply.github.com> | 2014-03-06 17:07:50 -0800 |
| commit | 5383d37925289dad8006b3d3cc0f012c84756b21 (patch) | |
| tree | 16abd071a7fd0e7b80f09879c4607978242925ca /FAQ.md | |
| parent | 10932b8f9010a2979e6c5903f2f656d4e816ddd7 (diff) | |
| download | qmk_firmware-5383d37925289dad8006b3d3cc0f012c84756b21.tar.gz qmk_firmware-5383d37925289dad8006b3d3cc0f012c84756b21.zip | |
Updated FAQ (markdown)
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -11,9 +11,10 @@ See [Issue #99](https://github.com/tmk/tmk_keyboard/issues/99). ## USB stack: LUFA or PJRC? Use **LUFA**. -**PJRC** stack won't be supported actively anymore. There is no reason to hesitate to use LUFA except for binary size(about 1KB lager?). See also [Issue #50](https://github.com/tmk/tmk_keyboard/issues/50) and [Issue #58](https://github.com/tmk/tmk_keyboard/issues/58). +**PJRC** stack won't be supported actively anymore. There is no reason to hesitate to use LUFA except for binary size(about 1KB lager?). But **PJRC** is still very useful for debug and development purpose. +See also [Issue #50](https://github.com/tmk/tmk_keyboard/issues/50) and [Issue #58](https://github.com/tmk/tmk_keyboard/issues/58). + -But **PJRC** is still very useful for debug and development purpose. # Degug Console ## hid_listen can't find device |