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.
Please, get this garbage out of the kernel. If it isn't there to talk to hardware, third party code has no place in the kernel. The same shit that Crowdstrike did could easily happen with any of these useless anticheats.
No way in hell.
I don't disagree, but today the blame lies with CrowdStrike, not Windows. As much as I hate defending Windows.
Yes, coincidence.
I can't disagree with you there.
Should have not trusted a third party to install proprietary code into the kernel. It's not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.
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.
It's also a "don't allow third party proprietary shit into your kernel" issue. If the driver was open source it would actually go through a public code review and the issue would be more likely to get caught. Even if it did slip through people would publically have a fix by now with all the eyes on the code. It also wouldn't get pushed to everyone simultaneously under the control of a single company, it would get tested and packaged by distributions before making it to end users.
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).
NVK is already usable, performancr isn't 100% of the proprietary driver but I play Overwatch on NVK at 165FPS on my RTX3070 laptop a lot, low settings but very playable. This is with an Optimus configuration (VRR Freesync panel on AMD iGPU) in GNOME Wayland.
Mastodon added text search a while ago.