From: Thomas Winischhofer <thomas@winischhofer.net>
To: arjanv@redhat.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ioctl number 0xF3
Date: Sat, 22 May 2004 14:39:47 +0200 [thread overview]
Message-ID: <40AF4A13.4020005@winischhofer.net> (raw)
In-Reply-To: <1085228451.14486.0.camel@laptop.fenrus.com>
Arjan van de Ven wrote:
> On Sat, 2004-05-22 at 14:08, Thomas Winischhofer wrote:
>
>>I would like to reserve ioctl's 0xF3 00-40 for the SiS framebuffer
>>device driver (2.4 and 2.6).
>>
>>Any oppositions?
>
>
> well you don't say what you want to use it for.... so nobody can see if
> those ioctls should become generic, if they are 32/64 bit safe etc etc.
> Might be a good idea to post the ioctl interface to the list as well.
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. The goal is to be able to write a
program similar to what sisctrl is for X (see my website for details on
sisctrl).
I have no list yet as I first wanted to know if somebody opposes for
reasons like 0xf3/0x0-0x40 being used by another driver already. I
quickly grep-ed but found none.
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).
Thomas
--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net http://www.winischhofer.net/
twini AT xfree86 DOT org
next prev parent reply other threads:[~2004-05-22 12:40 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 [this message]
2004-05-22 12:51 ` Arjan van de Ven
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=40AF4A13.4020005@winischhofer.net \
--to=thomas@winischhofer.net \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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