So, not the droid we Are looking for… :(

From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.

This looks the most promising. I’ll take a closer look. Does it provide a rtsp stream?

How about just having a button on a fob/phone which initiates comms, like in the good old days. You can’t relay the signal if there isn’t one till you press the button. But that isn’t sexy and it’s too similar to traditional cars, so they won’t do it.

Any PC that has virtualization features can be used. Unless it’s very old, I’d say it’s supported. But it may not be enabled in the bios by default. It’s called VT-x for Intel and AMD-v for AMD, I think. But both are supported for at least 10 years on almost any PC.

It’s a hypervisor level virtual machine host and you can use it to install multiple os’s on the same machine with little overhead. I’ve been running haos like that for a few months now and I’m super satisfied.