summaryrefslogtreecommitdiff
path: root/keyboards/tv44
diff options
context:
space:
mode:
authorFred Sundvik <fsundvik@gmail.com>2016-08-20 03:22:16 +0300
committerFred Sundvik <fsundvik@gmail.com>2016-08-20 03:56:48 +0300
commitda226e61261e0c11e678d2086c00b2a45726083e (patch)
tree3157d1db1b8f35782e25533e62a0b46bcb42fc99 /keyboards/tv44
parentb4c75569b0bc2f3ba9a7766ab64ff504fad3836e (diff)
Update keyboard readme files with new makefile instructions
Diffstat (limited to 'keyboards/tv44')
-rw-r--r--keyboards/tv44/readme.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/keyboards/tv44/readme.md b/keyboards/tv44/readme.md
index e3b557fe2d..4f691a4ca0 100644
--- a/keyboards/tv44/readme.md
+++ b/keyboards/tv44/readme.md
@@ -13,16 +13,16 @@ Depending on which keymap you would like to use, you will have to compile slight
### Default
-To build with the default keymap, simply run `make`.
+To build with the default keymap, simply run `make default`.
### Other Keymaps
Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create a folder with the name of your keymap in the keymaps folder, and see keymap documentation (you can find in top readme.md) and existant keymap files.
-To build the firmware binary hex file with a keymap just do `make` with `keymap` option like:
+To build the firmware binary hex file with a keymap just do `make` with a keymap like this:
```
-$ make keymap=[default|jack|<name>]
+$ make [default|jack|<name>]
```
Keymaps follow the format **__keymap.c__** and are stored in folders in the `keymaps` folder, eg `keymaps/my_keymap/` \ No newline at end of file