Valentin David@ada_magicat @pojntfx But I think those work. I have been using multiple USB to serial adapters without issues. It would be interesting to know if that is read-only only through the portal.
@ada_magicat @pojntfx I might misremember. I think maybe your user has to be in group "dialout".
Felicitas Pojtinger is in 🇪🇺@Valentin @ada_magicat Yeah, makes sense, I think my user does have access to this. I think it might be more of a "the USB portal doesn't do what I'd expect it too" kind of thing? I just get the raw USB node, but that the wrong layer of abstraction and I can't claim it bc the kernel already has a driver and creates a ttySX for it. I mean I could use like libftdi or smth but that feels wrong? Any thoughts, am I missing something here? https://mastodon.social/@pojntfx/116251786224520566
@Valentin @ada_magicat On the web platform I'd be using WebSerial here
@Valentin @ada_magicat Hmmm, yeah so I went down the libtfdi route and actually got it to work, but like I mentioned I had to unload the kernel driver, mess with udev/chmod the raw USB node and stuff which sounds like the wrong way to do it. Unless I'm missing something and there is a way to get the ttySX via the USB portal I think the best way forward might be to implement https://github.com/flatpak/xdg-desktop-portal/issues/229 - would probably be simple given that it's so close to the USB portal.
@Valentin @ada_magicat (& in the meantime I'll use the USB portal for enumeration + --device=all as a hack to get the ttySX for the USB device instead of the raw USB node)