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

[Bug] Currently-shipping Libra Mini boards not detectable by Vial due to changed productId #377

Closed
sehrgut opened this issue Feb 21, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@sehrgut
Copy link

sehrgut commented Feb 21, 2023

Describe the Bug

The Libra Mini definition in Vial expects productId 0x4C24, but currently-shipping boards have productId 0x4C23. The existing definition is otherwise fully compatible with 0x4C23 boards.

System Information

Keyboard: Libra Mini
Revision (if applicable): 0x4C23 putative rev. 2
Operating system: n/a
qmk doctor output: n/a

Any keyboard related software installed?
n/a

Additional Context

Files currently working with 0x4C23 boards: https://gist.github.com/sehrgut/622edc0f0e3a75bcff367c4cff2a436a

@sehrgut sehrgut added the bug Something isn't working label Feb 21, 2023
@xyzz
Copy link
Contributor

xyzz commented Feb 21, 2023

Vial doesn't actually use vendorId or productId for the vial firmware. It is only used in VIA backwards compatibility mode. So if the keyboard's not showing up, that means it was not flashed with the vial firmware. In general I consider VIA backwards compatibility to be mostly deprecated, so we will not act on this issue.

My suggestions are:

  • check with the keyboard vendor if the Vial firmware is available for that keyboard, download and flash it
  • consider using the VIA application for keyboards flashed with VIA firmware

@xyzz xyzz closed this as completed Feb 21, 2023
alextverdyy pushed a commit to alextverdyy/vial-qmk that referenced this issue Mar 17, 2024
This contains commit from da78eb3759b8..9d7a7f904ed1:

    9d7a7f90 Merge pull request vial-kb#382 from KarlK90/fix/rp2040-i2c-speeds
    70119934 Merge pull request vial-kb#383 from
             KarlK90/fix/rp2040-usb-get-status-request
    1a1bbe6c rp2040: usb: fix usb_lld_get_status functions
    7d9212dd rp2040: i2c: fix speed calculation
    fb67e502 Merge pull request vial-kb#377 from 1Conan/sn32_fix_registry
    e72939ef SN32: update registry
    5b4836ca Merge pull request vial-kb#376 from dexter93/sn32_usb_v2
    5ded9de9 sn32: usb: do NOT clear interrupt status until handled
    Leftover Sonix reference code cleanup. Sometimes when there is
    traffic on more than 1 ep's packets would be dropped before they
    could be handled. Clearing the status flags after handling them
    takes care of it.
    e9a4a512 sn32: usb: only activate interrupts on lld start
    e4a35d1c sn32: fix host remote wakeup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants