view the rest of the comments
Steam Hardware
A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to Steam Hardware or Steam OS in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
Update! It looks like it won't be too difficult to implement on Windows either! I did some poking around with RWEverything and the LED controller memory space is right there ready to be poked starting at address 0x0DE8 (IO port space). I manually poked the enable, LED color, and mode registers and could change the LEDs accordingly. This is easily achievable with a PawnIO module that mimics the sysfs entries from the Linux driver and I already have one partially written. I tested that PawnIO was able to enable/disable the LEDs and it could, but more complex interactions will require defining some ioctls and writing an OpenRGB implementation that mirrors the Linux one. Currently setting up my Windows build environment on the Steam Machine.