Software Engineer, Linux Enthusiast, OpenRGB Developer, and Gamer

Lemmy.world Profile: https://lemmy.world/u/CalcProgrammer1

  • 0 Posts
  • 102 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2021

help-circle







  • Linux works well on supported ARM platforms, but the problem is that a lot of ARM platforms aren’t supported. I recently got a Xiaomi Pad 5 Pro (had to import it as it’s a China-only model) and put postmarketOS on it. The experience is surprisingly good. Paired with a Bluetooth keyboard/touchpad, it is basically as functional as a normal light-duty Linux laptop except for the lack of x86 support, which mostly just means no gaming. I have been attempting to run Steam via box64 and FEX, but pmOS isn’t a supported distro for that so I have been trying in a Docker container and in Distrobox. I managed to get it started but it crashes due to steamwebhelper, and I think it’s a dependency or configuration issue. Otherwise, for browsing, coding, videos, terminal use, office, etc. it’s great and the battery life is amazing compared to my laptop. This is on a Snapdragon 870. Open source games run and they can hit 120fps on the 120Hz screen. I hope to see ARM support continue to improve, but I am worried about bootloader locks on these new ARM Windows machines.



  • I’m not sure about FF specifically, but 99% of the time you’re connecting a microcontroller to a PC you’re doing so over a serial port (UART) of some sort. It may be a physical COM port or it may be a USB to serial adapter or even a purely virtual serial port over a USB connection, but the methodology is all the same. Unless you are running a serial terminal on that port (as in, a commandline on your PC served on the given /dev/ttyX interface, not a terminal emulator letting you read/write from the port), the microcontroller can’t just run scripts on the PC. Instead, you will want to write a script/program that opens the port and waits for a command to be sent from the microcontroller, then that listener script can execute whatever functionality you require. Note that only one application can have the port active at a time, so if your listener is a separate program from your event handler, you will have to close the port on the listener before running the handler, then reopen the port on the listener once the handler is done so it can start listening for the next event. Better to just make it all one program that is always running on the PC and does both listening for events and handling them so there’s only one program that needs access to the serial port.


  • It’s not specific to Microsoft, but the general idea of letting proprietary software install whatever it wants whenever it wants directly into your kernel is a bad idea regardless. If the user had any control over this update process, organizations could do small scale testing themselves before unleashing the update on their entire userbase. If it were open source software, the code would be reviewed by many more eyes and tested independently by many more teams before release. The core issue is centralizing all trust on one organization, especially when that organization is a business and thus profit-driven above all else which could be an incentive to rush updates.



  • Who knew that allowing, no, PAYING third parties to inject whatever the fuck they want encrypted proprietary binary blobs into the highest privilege and most dangerous level of your operating system without any user acknowledgement or third party code review could possibly have negative consequences?

    This is also why we shouldn’t be allowing kernel anticheat games on our PCs by the way. One day Crowdstrike, the next day it could be Riot Vanguard. Proprietary shitware has no place in your kernel (though in Windows’ case the entire kernel itself is proprietary, maybe do something about that next).





  • I’m not familiar with KDE’s new feature yet, but if it only supports sysfs LEDs then it won’t control 99% of keyboards. Few RGB keyboards have drivers that expose this interface. Most RGB keyboards are controlled from userspace on their official software on Windows, and that’s also what most Linux projects that control RGB devices including my OpenRGB project do. I wonder if it would be possible to write an OpenRGB plugin/script that exposes a virtual /sys/class/leds/openrgb device that KDE could talk to, then translate that into OpenRGB calls to set the color on all available devices. It doesn’t sound too difficult.