From: Anatolij Gustschin <agust@denx.de>
To: "Jenkins, Clive" <Clive.Jenkins@xerox.com>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org,
lethal@linux-sh.org, Timur Tabi <timur@freescale.com>,
yorksun@freescale.com
Subject: Re: [PATCH] fsl-diu-fb: remove the ioctl interface
Date: Thu, 23 Jun 2011 11:26:04 +0000 [thread overview]
Message-ID: <20110623132604.1a6d0d71@wker> (raw)
In-Reply-To: <929D3CED81F34E43887A393170D66FB90484A280@GBRSUN01MS002.eu.xerox.net>
On Wed, 22 Jun 2011 11:39:49 +0100
"Jenkins, Clive" <Clive.Jenkins@xerox.com> wrote:
...
> > > Removing the ioctl interface also allows us to clean up the header
> file and
> > > remove other unusued stuff.
> >
> > No! We are using ioctl interface of this driver in many video
> > rendering applications on overlay planes on huge number of boards.
> > So, please don't remove it.
...
> Can you make available your application code by posting a link to it?
I do not have the code of the real applications since I didn't wrote
it. All I can share is the test and sample code that I used when working
on driver fixes:
test-app: http://pastebin.com/J2RvKb6n
HTH,
Anatolij
WARNING: multiple messages have this Message-ID (diff)
From: Anatolij Gustschin <agust@denx.de>
To: "Jenkins, Clive" <Clive.Jenkins@xerox.com>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org,
lethal@linux-sh.org, Timur Tabi <timur@freescale.com>,
yorksun@freescale.com
Subject: Re: [PATCH] fsl-diu-fb: remove the ioctl interface
Date: Thu, 23 Jun 2011 13:26:04 +0200 [thread overview]
Message-ID: <20110623132604.1a6d0d71@wker> (raw)
In-Reply-To: <929D3CED81F34E43887A393170D66FB90484A280@GBRSUN01MS002.eu.xerox.net>
On Wed, 22 Jun 2011 11:39:49 +0100
"Jenkins, Clive" <Clive.Jenkins@xerox.com> wrote:
...
> > > Removing the ioctl interface also allows us to clean up the header
> file and
> > > remove other unusued stuff.
> >
> > No! We are using ioctl interface of this driver in many video
> > rendering applications on overlay planes on huge number of boards.
> > So, please don't remove it.
...
> Can you make available your application code by posting a link to it?
I do not have the code of the real applications since I didn't wrote
it. All I can share is the test and sample code that I used when working
on driver fixes:
test-app: http://pastebin.com/J2RvKb6n
HTH,
Anatolij
next prev parent reply other threads:[~2011-06-23 11:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 21:27 [PATCH] fsl-diu-fb: remove the ioctl interface Timur Tabi
2011-06-21 21:27 ` Timur Tabi
2011-06-21 22:38 ` Anatolij Gustschin
2011-06-21 22:38 ` Anatolij Gustschin
2011-06-21 23:13 ` Tabi Timur-B04825
2011-06-21 23:13 ` Tabi Timur-B04825
2011-06-22 20:11 ` Anatolij Gustschin
2011-06-22 20:11 ` Anatolij Gustschin
2011-09-21 2:10 ` Tabi Timur-B04825
2011-09-21 2:10 ` Tabi Timur-B04825
2011-09-21 8:29 ` Anatolij Gustschin
2011-09-21 8:29 ` Anatolij Gustschin
2011-06-22 10:39 ` Jenkins, Clive
2011-06-22 10:39 ` Jenkins, Clive
2011-06-23 11:26 ` Anatolij Gustschin [this message]
2011-06-23 11:26 ` Anatolij Gustschin
2011-06-23 11:29 ` Tabi Timur-B04825
2011-06-23 11:29 ` Tabi Timur-B04825
2011-06-23 11:39 ` Anatolij Gustschin
2011-06-23 11:39 ` Anatolij Gustschin
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=20110623132604.1a6d0d71@wker \
--to=agust@denx.de \
--cc=Clive.Jenkins@xerox.com \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
--cc=yorksun@freescale.com \
/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.