> > > Halt endpoints by doing a "wrong direction" I/O ... read from an IN endpoint
> > > (instead of writing to the host), or write to an OUT endpoint (instead of
> > > reading what it wrote). This idiom avoids use of ioctls, and makes use
> > > of a code path that would otherwise just return an error.
> >
> > That is worse than an ioctl.
>
> No.
>
> > Read and write should transfer data, not change status of an io channel.
>
> Sounds like a valid thing for a special purpose fs to do (is simple, and
> can be done in any language, and doesn't require special thunking ioctl
> layer.)
That depends on whether you want to design a clean API, or you are
driven by avoiding ioctl, which is a valid part of the Unix API, at all cost
and your overriding concern are shell scripts.
You are treating write like ioctl. Using the syscall actually designed
for this is the clean solution. Write writes data, that's what it is meant
for.
Regards
Oliver
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
