#libusb — Public Fediverse posts

USB, Abstracted

https://fed.brid.gy/r/https://hackaday.com/2026/04/09/usb-abstracted/

USB, Abstracted

https://fed.brid.gy/r/https://hackaday.com/2026/04/09/usb-abstracted/

Rust Drives a Linux USB Device https://hackaday.com/2025/06/26/rust-drives-a-linux-usb-device/ #LinuxHacks #libusb #linux #rust #usb

Rust Drives a Linux USB Device - In theory, writing a Linux device driver shouldn’t be that hard, but it is harder ... - https://hackaday.com/2025/06/26/rust-drives-a-linux-usb-device/ #linuxhacks #libusb #linux #rust #usb

#libusb 1.0.28 RC1 has been released (#USB / #API) https://libusb.info/

Considering the Windows editor for my #DNAfx GiT Core won't run on neither Wine nor any VM, I've spent the past few days trying to reverse engineer its USB protocol, in order to write a basic editor for Linux of my own. It's been interesting so far to play with #libusb (I can already kinda talk to the device), especially coming from the perspective of a network developer, but I have some doubts on how #USB communication works in general: is there anyone around here that can clarify a few points?

Considering the Windows editor for my #DNAfx GiT Core won't run on neither Wine nor any VM, I've spent the past few days trying to reverse engineer its USB protocol, in order to write a basic editor for Linux of my own. It's been interesting so far to play with #libusb (I can already kinda talk to the device), especially coming from the perspective of a network developer, but I have some doubts on how #USB communication works in general: is there anyone around here that can clarify a few points?

Considering the Windows editor for my #DNAfx GiT Core won't run on neither Wine nor any VM, I've spent the past few days trying to reverse engineer its USB protocol, in order to write a basic editor for Linux of my own. It's been interesting so far to play with #libusb (I can already kinda talk to the device), especially coming from the perspective of a network developer, but I have some doubts on how #USB communication works in general: is there anyone around here that can clarify a few points?

Considering the Windows editor for my #DNAfx GiT Core won't run on neither Wine nor any VM, I've spent the past few days trying to reverse engineer its USB protocol, in order to write a basic editor for Linux of my own. It's been interesting so far to play with #libusb (I can already kinda talk to the device), especially coming from the perspective of a network developer, but I have some doubts on how #USB communication works in general: is there anyone around here that can clarify a few points?

Considering the Windows editor for my #DNAfx GiT Core won't run on neither Wine nor any VM, I've spent the past few days trying to reverse engineer its USB protocol, in order to write a basic editor for Linux of my own. It's been interesting so far to play with #libusb (I can already kinda talk to the device), especially coming from the perspective of a network developer, but I have some doubts on how #USB communication works in general: is there anyone around here that can clarify a few points?

Today I discovered a pretty cool utility for listing USB devices! 🔌

🌸 **cyme**: A modern and cross-platform lsusb!

🔥 Displays manufacturer, serial number, speed, current information (mA) and more!

🦀 Written in Rust!

⭐ GitHub: https://github.com/tuna-f1sh/cyme

#rustlang #lsusb #usb #devices #utility #commandline #tool #libusb

does anyone knows a simple way to handle hotplug #usb devices with #libusb ?

I could really use some #libusb experts opinion on getting this function faster. The round trip takes 100~200 uS and is just too slow, but async read causes race conditions.
A single write takes 30 uS (async). Ive already removed all overhead on the device side code but the time stays the same. #tinyusb #rp2040

via @loudfpv

https://mastodon.social/@loudfpv/113080861770413089

Any LIBUSB Async (linux) experts here? I want to improve speed between usbsid and PC. Unfortunately I am running into race conditions causing packets from device to pc misalign, e.g. the callback gets called more then expected, or too late. Async send and sync on read is too slow.
#libusb #async

#libusb 1.0.27 has been released (#USB) https://libusb.info/

It works, but everything is hardcoded. Need to add some configuration system. #streamdeck #WriteInC #libusb

It works, but everything is hardcoded. Need to add some configuration system. #streamdeck #WriteInC #libusb

It works, but everything is hardcoded. Need to add some configuration system. #streamdeck #WriteInC #libusb

It works, but everything is hardcoded. Need to add some configuration system. #streamdeck #WriteInC #libusb

It works, but everything is hardcoded. Need to add some configuration system. #streamdeck #WriteInC #libusb

Can anyone recommend a #framework that allows relatively easy cross-platform (#Android, #Windows, #Linux) development?
Needs to be able to:
- Open #USB webcam stream
- Call #ffmpeg
- Send USB vendor control transfers (or calls to #libusb)
- GUI

:BoostOK:

I really don't want to write code two times (and dislike Android app dev), but recently realized that I'd really like for my upcoming #P2Pro viewer to run on Android too.

But if there is no such thing, I'll stick to desktop only for now :/

Can anyone recommend a #framework that allows relatively easy cross-platform (#Android, #Windows, #Linux) development?
Needs to be able to:
- Open #USB webcam stream
- Call #ffmpeg
- Send USB vendor control transfers (or calls to #libusb)
- GUI

:BoostOK:

I really don't want to write code two times (and dislike Android app dev), but recently realized that I'd really like for my upcoming #P2Pro viewer to run on Android too.

But if there is no such thing, I'll stick to desktop only for now :/

Can anyone recommend a #framework that allows relatively easy cross-platform (#Android, #Windows, #Linux) development?
Needs to be able to:
- Open #USB webcam stream
- Call #ffmpeg
- Send USB vendor control transfers (or calls to #libusb)
- GUI

:BoostOK:

I really don't want to write code two times (and dislike Android app dev), but recently realized that I'd really like for my upcoming #P2Pro viewer to run on Android too.

But if there is no such thing, I'll stick to desktop only for now :/

Can anyone recommend a #framework that allows relatively easy cross-platform (#Android, #Windows, #Linux) development?
Needs to be able to:
- Open #USB webcam stream
- Call #ffmpeg
- Send USB vendor control transfers (or calls to #libusb)
- GUI

:BoostOK:

I really don't want to write code two times (and dislike Android app dev), but recently realized that I'd really like for my upcoming #P2Pro viewer to run on Android too.

But if there is no such thing, I'll stick to desktop only for now :/

Can anyone recommend a #framework that allows relatively easy cross-platform (#Android, #Windows, #Linux) development?
Needs to be able to:
- Open #USB webcam stream
- Call #ffmpeg
- Send USB vendor control transfers (or calls to #libusb)
- GUI

:BoostOK:

I really don't want to write code two times (and dislike Android app dev), but recently realized that I'd really like for my upcoming #P2Pro viewer to run on Android too.

But if there is no such thing, I'll stick to desktop only for now :/

Day 2 of my posting adventures to finally figure out what is going on with my build of #libuhd #libusb on #openbsd :openbsd:

https://sourceforge.net/p/libusb/mailman/message/37796867/

:boost_ok: boosts would be v helpful in case anyone has seen something like this before, esp from bsd folks or sdr folks #ham #sdr #bsd

if any of my :openbsd: friends have some time to devote to a mystery, I don't know #OpenBSD's USB stack / ugen well enough to reason through the logs, so far everyone I've reached out to haven't been able to point me in the direction of a smoking gun yet #bsd #libusb

https://marc.info/?t=167993667800007&r=1&w=2

With libusb_get_bus_number(), and libusb_get_port_numbers(), one can easily construct a path like /sys/bus/usb/devices/{BUS}-{PORTS} to access the string descriptors as "product", "manufacturer", and "serial" (if present). And /sys/bus/usb/devices/{BUS}-{PORTS}:{CONFIGNUM}-{INTERFACENUM} has "interface" for the interface string descriptor (if present).

#projects #xdebug #libusb #workarounds

With libusb_get_bus_number(), and libusb_get_port_numbers(), one can easily construct a path like /sys/bus/usb/devices/{BUS}-{PORTS} to access the string descriptors as "product", "manufacturer", and "serial" (if present). And /sys/bus/usb/devices/{BUS}-{PORTS}:{CONFIGNUM}-{INTERFACENUM} has "interface" for the interface string descriptor (if present).

#projects #xdebug #libusb #workarounds

Annoying. libusb requires you to open a device before reading string descriptors (necessitating you have read/write permission because libusb only opens devices RW).

On modern Linux (and I believe on Windows and OSX) this is not actually necessary and makes enumeration and reporting errors to users that much more complicated than need be.

This feature has been discussed, but there has been no forward motion, it seems:
https://github.com/libusb/libusb/issues/866

#projects #xdebug #libusb #grumbles

Yesterday I've learned what USB filter drivers are on Windows and that it's apparently pretty easy to install libusb0 as one. (Thanks @patagona)

Having done that, my initial plan worked on the second try. I can now send the command for switching the color palette, wohoo \o/

I only needed to make sure that I send the USB control transfers after the video capture has already been started, otherwise the call to #libusb will just hang indefinitely for whatever reason.

#P2Pro #reveng

Yesterday I've learned what USB filter drivers are on Windows and that it's apparently pretty easy to install libusb0 as one. (Thanks @patagona)

Having done that, my initial plan worked on the second try. I can now send the command for switching the color palette, wohoo \o/

I only needed to make sure that I send the USB control transfers after the video capture has already been started, otherwise the call to #libusb will just hang indefinitely for whatever reason.

#P2Pro #reveng

Yesterday I've learned what USB filter drivers are on Windows and that it's apparently pretty easy to install libusb0 as one. (Thanks @patagona)

Having done that, my initial plan worked on the second try. I can now send the command for switching the color palette, wohoo \o/

I only needed to make sure that I send the USB control transfers after the video capture has already been started, otherwise the call to #libusb will just hang indefinitely for whatever reason.

#P2Pro #reveng

Yesterday I've learned what USB filter drivers are on Windows and that it's apparently pretty easy to install libusb0 as one. (Thanks @patagona)

Having done that, my initial plan worked on the second try. I can now send the command for switching the color palette, wohoo \o/

I only needed to make sure that I send the USB control transfers after the video capture has already been started, otherwise the call to #libusb will just hang indefinitely for whatever reason.

#P2Pro #reveng

Yesterday I've learned what USB filter drivers are on Windows and that it's apparently pretty easy to install libusb0 as one. (Thanks @patagona)

Having done that, my initial plan worked on the second try. I can now send the command for switching the color palette, wohoo \o/

I only needed to make sure that I send the USB control transfers after the video capture has already been started, otherwise the call to #libusb will just hang indefinitely for whatever reason.

#P2Pro #reveng

Als Hardware-Nerd hat man es schwer. Da habe ich nun meine kleinen #Atmel #attiny85 hier und kann sie auch prima für USB-Übertragung einsetzen, wenn ich nur Ahnung von der anderen Seite hätte, sei es Win oder Linux. Es gibt die #libusb API, aber nix für mich, welcher weder in C noch in Python zuhause ist sondern eher am Lötkolben. Den Traum, #USB ähnlich behandeln zu können wie #RS232 habe ich wohl ausgeträumt. 😢

Mein POS-Kundendisplay läuft nun auch unter Linux.
Es reicht schon, das Gerät mit #PyUSB über #libusb aufzumachen, die erste (und einzige) Konfiguration zu aktivieren und die seriellen Daten auf den per Wireshark ermittelten #USB-Endpoint zu schreiben.

Ich muss jetzt noch mal abwarten ob irgendwann der Puffer platzt weil ich keine Daten abhole, aber bisher funktioniert es und so viel hat ein #Display eh nicht zu erzählen.

@overflo