forked from forks/qmk_firmware
Updated FAQ (markdown)
This commit is contained in:
parent
a25df9432b
commit
10932b8f90
6
FAQ.md
6
FAQ.md
|
@ -9,9 +9,11 @@ It is no longer recommended and may cause some problem.
|
||||||
See [Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
|
See [Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
|
||||||
|
|
||||||
## USB stack: LUFA or PJRC?
|
## 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?).
|
Use **LUFA**.
|
||||||
|
|
||||||
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?). 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
|
# Degug Console
|
||||||
## hid_listen can't find device
|
## hid_listen can't find device
|
||||||
|
|
Loading…
Reference in a new issue