Messages in this thread | | | Date | Sun, 28 Nov 2004 15:30:19 +0100 | From | Tomas Carnecky <> | Subject | Re: Problem with ioctl command TCGETS |
| |
Al Viro wrote: > On Sun, Nov 28, 2004 at 01:52:41PM +0100, Miklos Szeredi wrote: > >>>>>Think read(2)/write(2). We already have several barfbags too many, >>>>>and that includes both ioctl() and setsockopt(). We are stuck with >>>>>them for compatibility reasons, but why the hell would we need yet >>>>>another one? >>>> >>>>You can't replace either ioctl() or setsockopt() with read/write can >>>>you? Both of them set out-of-band information on file descriptors. >>> >>>Out-of-band == should be on a separate channel... >> >>Tell me how? E.g. how would you set/get sound stream parameters if >>not with ioctl()? > > > Have several related files.
You mean.. like nvidia? /dev/nvidiactl /dev/nvidia0 /dev/nvidia1 /dev/nvidia2 and do read/write on /dev/nvidiactl (instead on ioctl)?
tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |