> I'm almost fully finished implementing a patch which provides a device node
> per endpoint which would remove many of the ioctl's.

You should only need one ioctl() which is the 'what device' you issue first.

> So, this is a no win situation. Keep support for 2.2 in the form of ioctl's
> and get flamed for making everything an ioctl, or move forward and fix the
> deficiencies at the cost of making 2.2 support exceedingly difficult.
> 
> Once again, my opinion is to not hold down USB with legacy baggage in the
> form of 2.2 support.

I'd like to keep minimal baggage but encourage people to do it the right
way. The single ioctl then the same API is as close as I can see to avoiding
the two API problem




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to