View Single Post
Old 02-13-2025, 04:52 AM   #6
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,449
Karma: 107078855
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by kovidgoyal View Post
One could use a user maintained mapping of filesystem path to usb vendor/product/bcd ids to impleent this, with a fake device being detected and the appropriate driver being called. But its a fair bit of work for a rather niche use case so not sure I want to spend the time.

There will be some subtleties like how to detect disconnect. And of course it will only work for USBMS based devices, not MTP based ones.
I rather suspect that given the progress on Crostini since (amazingly for google) that it exited Beta, that sooner or later both USBMS & MTP will work normally in the Linux container. They sometimes do now if the device isn't ebabbled for Android app in External Storage in regular settings.
Quoth is offline   Reply With Quote