Re: Forcing a USB device to "ugen"

> On Mar 26, 2024, at 2:49 AM, Martin Husemann <[email protected]> wrote:

> It is also not *that* intrusive as it may sound at first look:
> basically we need a central registry that collects all the
> identification data (vid,pid,strings and what have you) plus the parent
> and the device pointer, and a flag if this is a device claimed by some
> driver or one of the currently visible ugen* things.

I was thinking about this while sipping my first cup of coffee this morning..

I think the right model is for a “ugen” or what-have-you attach to uhub, and then for the kernel drivers to attach to ugen (either claim the whole device or attach to individual interfaces).

-- thorpej