usbipd-win VS refterm

If (like me) you're stuck on Windows, WSL2 is really awesome. It's super fast, and requires very minimal setup to get it up and running. The VS Code integration is superb. You can even connect USB devices to WSL now, which makes it very suitable for embedded. You get nearly the performance of a full OS install, unlike a typical VM. On my machine it's about 50% faster than Virtualbox.

ADS-B is a protocol used by aircrafts to broadcast their position, altitude, speed, and other information. Nowadays, the majority of aircrafts broadcast ADS-B messages constantly. Anyone with the right equipment can listen to these messages. You can buy a relatively cheap USB dongle with an antenna on Amazon and install drivers for it on Linux. In my case I used usbipd-win to mount the USB device inside Ubuntu running in WSL2. Then I installed the Linux drivers and dump1090, a program that makes use of these drivers and then outputs ADS-B messages in a format that is easy to parse. While you can use dump1090 to display a neat table full of information about aircrafts, I wanted to use its raw output capabilities to parse ADS-B messages myself. It starts a simple TCP server that outputs raw ADS-B messages wrapped in Mode-S Beast frames. I'm not sure what Beast means, but I found something that looks like its spec here.

Anyway, in the meantime you can try using usbipd-win. Start with:

Hi, I'm using usbipd to redirect USB devices to a remote virtual machine (USB/IP) for my work and I'd like to know if the expansion cards are detected as their own devices, especially the Ethernet expansion card.

What about USB devices support ?

Is there any more integrate solution than:

https://github.com/dorssel/usbipd-win/

There is even a GUI available for usbip-win if you please. Start here: https://github.com/dorssel/usbipd-win

I installed usbipd as outlined here. When I run lsusb, I can see my USB drive:

Though I see https://github.com/dorssel/usbipd-win may actually work properly as a full usb passthrough now for WSL2?

For server (e.g. machine that provides devices), https://github.com/dorssel/usbipd-win is a bit more mature - they grabbed the driver infrastructure from virtualbox to handle the issues with code signing.

Check this project out. Works with WSL. Should work with Hyper-V too https://github.com/dorssel/usbipd-win

refterm, a terminal emulator proof of concept.

> licensing it so that they couldn’t even look at it

https://github.com/cmuratori/refterm/blob/main/LICENSE

It’s just GPL 2.0, what are you talking about!?

Are Microsoft employees vampires that will burn up instantly if they merely glance at GPL code or something?

This is sour grapes nonsense from Microsoft. “We don’t like your tone so we won’t even dignify your argument by considering it.”

At one point an MS employee said they would love to fix their code as suggested by Casey but he refused to even look at the YouTube video!

“I would love to hear your arguments but I refuse to listen to the sound of your voice.” is next-level dismissive.

You might also find https://github.com/cmuratori/refterm interesting.

Casey Muratori made a renderer/terminal a short while back. Might be a good reference of you intend to go that route. https://github.com/cmuratori/refterm

You keep complaining that it's not a fully working terminal. Casey, on the other hand, writes here: [1]

> These features are not designed to be comprehensive, since this is only meant to be a reference renderer, not a complete terminal.

[1] https://github.com/cmuratori/refterm#feature-support

After that post they did implement a full reference implementation:

https://github.com/cmuratori/refterm/commits/main

And there is movement in getting changes into the terminal itself:

https://github.com/microsoft/terminal/issues/10461

For a basic example of why you would want GPU acceleration, have a look at refterm: https://github.com/cmuratori/refterm

Even processes that you wouldn't think would be impacted by a terminal can be hurt relaly bad by your terminal's performance: your compiler's logs, etc. The GPU rendering part merely guarantees that your terminal sticks at 60FPS (or, whatever your refresh rate is) if the processing behind is efficient.