• 4grams@awful.systems
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 hours ago

    This is a great write up, not only in content, but also in spirit and tone. An enjoyable read beginning to end and inspires me to try more stuff.

  • voodooattack@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    6 hours ago

    This is amazing. I love discovering new/interesting developer blogs like this one, which is a challenge considering they’re all buried by SEO bullshit.

  • ILikeBoobies@lemmy.ca
    link
    fedilink
    arrow-up
    28
    ·
    12 hours ago

    Trivia you can use to woo potential partners Here’s 443 pages on generic HID implementations.

    My pants!

  • Tenderizer78@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    12 hours ago

    I would try doing this for my Intel WiFi/Bluetooth card that doesn’t support Linux (WiFi works anyway though). Since the CTRL key is dead (again) and the whole build of it is not to my liking I think I’ll get an old Windows 10 laptop to replace the whole system instead.

  • RollForInitiative@feddit.org
    link
    fedilink
    arrow-up
    7
    ·
    16 hours ago

    Interesting read. I wonder where OP got the specs for the device itself, i.E. what it expects in terms of data and what the response (interrupt) values mean?

    • killeronthecorner@lemmy.world
      link
      fedilink
      English
      arrow-up
      19
      ·
      16 hours ago

      To my surprise, Nanoleaf tech support responded to me within 4 hours, with a full description of the protocol that’s used both by the Desk Dock as well as their RGB strips. The docs mostly confirmed what I had already discovered independently, but there were a couple of other minor features as well (like power and brightness management) that I did not know about, which was helpful.

      Combo of investigating and a foot up from the manufacturer.

      When I’ve done this in the past for game controllers I’ve not received such an emphatic response (other than when I was working for the vendor).

      Did get some via FOI for a few other products though.

      • comfy@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        5 hours ago

        Yeah, props to the Nanoleaf team for helping the author out. Win-win. The author says at the end that they intend on sharing it around more once it has more polish, so I hope they upstream it properly and demonstrate to Nanoleaf that helping out volunteers helps their product reach more customers. (I know it’s iffy to suggest it’s ok to neglect Linux and let us sort it out ourselves, but if we get open-source drivers in the processes with the help of the company, I think that’s a net win)

    • IsoKiero@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      8
      ·
      16 hours ago

      Over the past few posts I’ve set up a Windows VM with USB passthrough, and attempted to reverse-engineer the official drivers, As I was doing that, I also thought I’d message the vendor and ask them if they could share any specifications or docs regarding their protocol. To my surprise, Nanoleaf tech support responded to me within 4 hours, with a full description of the protocol that’s used both by the Desk Dock as well as their RGB strips.