Skip to content

Commit

Permalink
direct links to releases to the bkb userspace instead
Browse files Browse the repository at this point in the history
  • Loading branch information
burkfers committed Sep 11, 2024
1 parent de4a16d commit c19e918
Show file tree
Hide file tree
Showing 5 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions fw/compile-firmware.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ This page details how to build your own firmware.
Building from source is useful to people who want to customize their keyboard and keymaps beyond what Via offers.
You will have to modify the keymap `C` code, and from there compile your firmware either using Github actions or the local command line.

If that seems too complicated, you can also use one of the [release firmware](https://github.com/Bastardkb/bastardkb-qmk/releases/latest) builds.
If that seems too complicated, you can also use one of the [release firmware](https://github.com/Bastardkb/qmk_userspace/releases/latest) builds.

# Pre-requisites

Expand Down Expand Up @@ -186,4 +186,4 @@ For how to flash your keyboard, take a look at the [how to flash your keyboard p
---

[flashing]: {{site.baseurl}}/fw/flashing.html
[bkbus]: https://github.com/Bastardkb/qmk_userspace
[bkbus]: https://github.com/Bastardkb/qmk_userspace
2 changes: 1 addition & 1 deletion fw/default-keymaps.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ parent: Firmware
This page contains reference pictures for all the default keymaps flashed onto the Bastard Keyboards.

Releases are available here:
https://github.com/Bastardkb/bastardkb-qmk/releases
https://github.com/Bastardkb/qmk_userspace/releases

For more information on the features from the Charybdis keymaps, see the [charybdis features][chary] page.

Expand Down
2 changes: 1 addition & 1 deletion fw/flashing.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,6 @@ If you use the `QK_BOOT` method, please note that your layout may now be mirrore

----
[build]: {{site.baseurl}}/fw/compile-firmware.html
[releases]: https://github.com/Bastardkb/bastardkb-qmk/releases
[releases]: https://github.com/Bastardkb/qmk_userspace/releases
[keymaps]: {{site.baseurl}}/fw/default-keymaps.html
[splitkb-whentoflash]: https://docs.splitkb.com/hc/en-us/articles/360011949679-When-do-I-need-to-flash-my-microcontroller
2 changes: 1 addition & 1 deletion help/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Received invalid protocol version from device

Outlined below are some steps, in order of complexity:
- make sure you use a chromium-based browser like edge, google chrome
- flash the [latest firmware version](https://github.com/Bastardkb/bastardkb-qmk/releases/latest)
- flash the [latest firmware version](https://github.com/Bastardkb/qmk_userspace/releases/latest)

### Custom udev rules

Expand Down
2 changes: 1 addition & 1 deletion hw/rp2040-community.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Controller | Pin-compatible | Flash size | Vbus detection | Notes

# Firmware compatibility

All controllers above marked as pin-compatible, and using the QMK default `W25Q080` second-stage bootloader, should be compatible out-of-the-box with the [Bastard Keyboard firmwares](https://github.com/bastardkb/bastardkb-qmk/releases) targeting the Splinky v3, _ie._ `splinky_3` firmwares.
All controllers above marked as pin-compatible, and using the QMK default `W25Q080` second-stage bootloader, should be compatible out-of-the-box with the [Bastard Keyboard firmwares](https://github.com/Bastardkb/qmk_userspace/releases).

## Bootloader

Expand Down

0 comments on commit c19e918

Please sign in to comment.