From: Tomas Carnecky <tom@dbservice.com>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
ecki-news2004-05@lina.inka.de, linux-kernel@vger.kernel.org
Subject: Re: Problem with ioctl command TCGETS
Date: Sun, 28 Nov 2004 15:30:19 +0100 [thread overview]
Message-ID: <41A9E0FB.8030001@dbservice.com> (raw)
In-Reply-To: <20041128130319.GB26051@parcelfarce.linux.theplanet.co.uk>
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
next prev parent reply other threads:[~2004-11-28 14:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 0:22 Problem with ioctl command TCGETS Ozan Eren Bilgen
2004-11-28 0:39 ` Al Viro
2004-11-28 9:59 ` Miklos Szeredi
2004-11-28 10:08 ` Jan Engelhardt
2004-11-28 10:18 ` Miklos Szeredi
2004-11-28 10:28 ` Bernd Eckenfels
2004-11-28 10:56 ` Wichert Akkerman
2004-11-28 11:52 ` Bernd Eckenfels
2004-11-28 11:22 ` Miklos Szeredi
2004-11-28 12:18 ` Al Viro
2004-11-28 12:32 ` Miklos Szeredi
2004-11-28 12:48 ` Al Viro
2004-11-28 12:52 ` Miklos Szeredi
2004-11-28 13:03 ` Al Viro
2004-11-28 14:30 ` Tomas Carnecky [this message]
2004-11-28 15:27 ` Al Viro
2004-11-28 18:23 ` Tomas Carnecky
2004-11-28 18:51 ` Miklos Szeredi
2004-12-10 4:01 ` Ingo Oeser
2004-11-28 13:20 ` Tomas Carnecky
2004-11-28 14:05 ` Al Viro
2004-11-28 13:07 ` Tomas Carnecky
2004-11-28 13:11 ` Al Viro
2004-11-28 13:19 ` Tomas Carnecky
2004-11-28 17:42 ` Alan Cox
2004-11-30 13:26 ` Pavel Machek
2004-11-30 15:46 ` Al Viro
2004-11-28 12:23 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A9E0FB.8030001@dbservice.com \
--to=tom@dbservice.com \
--cc=ecki-news2004-05@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.