Skip to content
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

Update info related to the issue with n!n 2 and underglow #1461

Closed
wants to merge 2 commits into from

Conversation

Xoffio
Copy link

@Xoffio Xoffio commented Sep 21, 2022

#885
I think it is important to add this info related to the issue with nice nano 2 and the underglow to avoid confusion.

Copy link
Contributor

@lesshonor lesshonor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this point, it might be best to close this PR.

@@ -105,6 +105,17 @@ If your board/shield uses LEDs that require the data sent in a different order,

:::

:::note

Currently, If you are using a nice nano 2, underglow won't work out of the box.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This is a bit too much of a blanket statement. Even when this PR was opened, some shields did have .overlay files for nice_nano_v2...
  2. While the discussion of moving to Zephyr's board versioning system is moot
    (related: Strip board revision so keymap file use only board name #1015, Underglow overlays for nice_nano don't work on nice_nano_v2 #885 (comment))
    ..."duplicate" nice_nano*.overlay files were added to in-tree shields in Zephyr 3.2 Upgrade #1499. Fortunately or unfortunately, that retroactively invalidates all the cases in which this statement was true.

To make this work you need to add an overlay in your `.keymap` file like this:

```
#include <../boards/shields/<board>/boards/nice_nano.overlay>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This proposed workaround is fragile (what if nice_nano.overlay doesn't exist?) and, well...doesn't quite seem congruent with ZMK's overall style.

Bodging things into a personal keymap is one thing, but I am doubtful that ZMK as a project wants to sanction approaches of this nature by adding them to the official documentation.

@caksoylar
Copy link
Contributor

Thanks @lesshonor, I believe Zephyr 3.2 update added all the v2 overlays for shields that already had the v1 ones, so we can close this.

@caksoylar caksoylar closed this Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants