InvertedParallax

Don't Trust Him!!!

He made Martin Scorsese cry, he took his picture, and he railed him raw, he railed Marty raw!

I need to explain to people why this is so amazingly stupid:

You are literally giving Europe an excuse to put tariffs on American goods and services, which they want to anyway, to encourage domestic producers.

Also, you're making it easier for them to buy directly from south Korea, Japan and even China, especially since those countries can't sell as easily to the US.

For Europe this is an absolute win/win.

But honestly, this sounds like a way for Trump to put pressure on Europe to back off on Ukraine, as he probably thinks the EU is reliant on US LNG, which is kind of isn't really.

Murderbot

It's not ... A great show?

But it's fucking cheap (small cast, limited sets so far), and it's trying to be charming.

It's the streaming equivalent of comfort food.

We need more content like this to keep streams full, then we have a few prestige shows like andor or whatever.

What we have now is crap writing burning prestige money (twot/LOTR-trop) and leaving us with unwatchable crap.

It’s not Bluetooth - it’s WiFi, using a proprietary blob for authentication.

You've literally missed my whole point.

Playstation link is this exact same thing, and btw, both controllers are dual-mode bluetooth and "high-speed wireless interface", which is basically wifi or wifi-direct or some proprietary variant.

My point is, why isn't it like Playstation link which just presents as HID devices and usb-audio devices, without a driver at all? Same low-latency, they even do LDAC.

if your input is barely too late for one 125Hz poll,

So those polls are generally isochronous to the USB bus transaction state, not based on polling frequency of the CPU, what happens is:

1. USB interrupt URB comes in to HCI controller,.URB descriptor written to descriptor chain.

2. Controller adds to descriptor chain, once chain length > WAT (| Timeout), interrupt and start processing incoming URBs.

3. In interrupt controller, follow chain, push URBs onto usb stack queue, trigger handler tasklet

4. Stack processes URB, routes to proper class driver

5. Class driver checks if URB has file handle open (or has open ref from drivers like HID/input).

6. If so, poll or other input read() returns value.

Now it's possible there are multi-input poll reads in games, and I'm doing linux of course.

For MSFT it's URB -> IRP -> WDM filter driver stack -> kernel32/directinput or win32 input stack (WNDPROCs after routing).

In any of these cases, I'm struggling to see how interrupts would come in faster with the same code on PC.

See, the same code probably runs on both MSFT and normal hardware, so it's going to have the same structure, unless you actually believe a dev team is optimizing input latency that much, that's often the lowest priority, they'll optimize video lag more because it's more noticeable. The engines themselves use DirectInput, and that's routed through to libinput in WINE, and the same for all devices.

Btw, DirectInput has a device-based interface, so it couldn't poll like this anyway, basically each controller has its own input queue that is round-robin and pluck stuff out of their input stream when available.

In any case, you're not getting the latency improvement, both because it's so different in software and because nothing can appreciate this.

I'm not trying to be extra autistic for no reason, I've just had to make these decisions before, and these are how we have to think.

I can respect that, I just think there should be a lot of pressure on MSFT to reprogram firmware to support linux natively.

The kernel has been desperately trying to move away from these 1-off, quirky drivers as they're impossible to maintain.

Firstly, it's not a real hub, it's an emulated hub, and you can do that emulating everything as USB 2.0.

Secondly you can have multiple hid interface endpoints on a single device.

Thirdly, you wouldn't be polling, these would be hid interrupt urbs, and you can storm them 1 per micropacket if you want, they just show up in the ehci buffers.

Finally, no human is overflowing the hid interface like this, not even 8 of them.

Hid is what should be required.

There are a million standards already here, I'd they really want to they can extend hid or something.

This is just a scrappy proprietary driver for no reason :(

First one was ok because of Chris P and Chris P. Ana De Armas did her bit too.

Second one just got lost.

My point is that the PS link doesn't need a dedicated driver, why does this one?

assume they didn’t want to emulate an eight-port USB hub on the dongle.

https://github.com/abcminiuser/lufa

Literally a kid did this in high school, this is without hardware support, just GPIO, but he also implemented the full stack on avrusbs and cortex-ms, and one thing he emulated was multiple devices on a hub.

Not in the south.

Their dedication to racism eclipses even their sexism, everything else is just in service to the greater goal.