Alex Nemirovsky wrote:

> If I understand the ugen correctly, these devices
> assign the minor number to be equal to a combination
> of the unit number and the endpoint number.  Since the
> rio uses three
> end points (control pipe, and two bulk transfer pipes
> in/out) we would have to change the userland
> stuff to search all the ugen devices for the rio and
> when found open up three devices instead of a single
> one.

Yes, that's the idea.


> The rio user land code also calls special ioctls
> ( which send out special vendor specific requests to
> the default control pipe)
> to the rio driver. Would we need to roll these ioctls
> out of the driver and back into the userland code?

Yes.



> Is this what you are proposing?

Yes.


>
> If so, it sounds like alot of the Linux userland stuff
> would be trashed.  It would be
> nice if we could just use the Linux tools since
> they will continue to make improvements to them.

Well, if you take at the latest version you'll see that the Linux userland
code is moving away from using a kernel driver.  They are going to use
what corresponds to ugen in Linux, accessed via their libusb.
We should implement libusb on top of ugen.


--

        -- Lennart