From: Arjan van de Ven <arjanv@redhat.com>
To: Thomas Winischhofer <thomas@winischhofer.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ioctl number 0xF3
Date: Sat, 22 May 2004 14:51:09 +0200 [thread overview]
Message-ID: <20040522125108.GB4589@devserv.devel.redhat.com> (raw)
In-Reply-To: <40AF4A13.4020005@winischhofer.net>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Sat, May 22, 2004 at 02:39:47PM +0200, Thomas Winischhofer wrote:
> I intend using them for controlling SiS hardware specific settings like
> switching output devices, checking modes against output devices,
> repositioning TV output, scaling TV output, changing gamma correction,
> tuning video parameters, and the like.
That doesn't in principle sound SiS specific. Sure the implementation will
be but the interface?
> And rest assured, they will be 32/64 bit safe. Not sure what you mean by
> "ioctl interface" here but have a look at the Matrox framebuffer driver
> which uses some 'n' ioctls for similar stuff (which in that way do not
> apply to the SiS hardware which is why I can't reuse them).
Ok this is exactly the point I was trying to make. Would it be possible to
have the "new" ioctl interface be such that they CAN be used by both matrox
and Sis ?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-22 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 12:08 ioctl number 0xF3 Thomas Winischhofer
2004-05-22 12:20 ` Arjan van de Ven
2004-05-22 12:39 ` Thomas Winischhofer
2004-05-22 12:51 ` Arjan van de Ven [this message]
2004-05-22 13:29 ` Thomas Winischhofer
2004-05-22 14:32 ` Francois Romieu
2004-05-22 15:37 ` Thomas Winischhofer
2004-05-23 1:35 ` Petr Vandrovec
2004-05-23 23:39 ` Francois Romieu
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=20040522125108.GB4589@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@winischhofer.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox