From: Arnd Bergmann <arnd@arndb.de>
To: Greg KH <gregkh@suse.de>
Cc: Ali Gholami Rudi <ali@rudi.ir>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Righi <righi.andrea@gmail.com>,
Krzysztof Helt <krzysztof.h1@wp.pl>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Philippe De Muyter <phdm@macqel.be>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] fbdev: add fillrect and copyarea ioctls
Date: Mon, 13 Jul 2009 20:53:12 +0200 [thread overview]
Message-ID: <200907132053.13032.arnd@arndb.de> (raw)
In-Reply-To: <20090713163530.GA22251@suse.de>
On Monday 13 July 2009, Greg KH wrote:
> On Mon, Jul 13, 2009 at 07:47:09PM +0430, Ali Gholami Rudi wrote:
> > Hi,
> >
> > Is there any reason for not adding these ioctls to fbdev? I searched
> > the net and couldn't any. Anyway, these patches simply implement those
> > ioctls.
>
> Have you also added the needed 32 vs. 64 bit handlers for these ioctls?
>
They are not there, but could be trivially added with
diff --git a/drivers/video/fbmem.c b/drivers/video/fbmem.c
index f8a09bf..ce107c4 100644
--- a/drivers/video/fbmem.c
+++ b/drivers/video/fbmem.c
@@ -1285,6 +1285,8 @@ static long fb_compat_ioctl(struct file *file, unsigned int cmd,
case FBIOPAN_DISPLAY:
case FBIOGET_CON2FBMAP:
case FBIOPUT_CON2FBMAP:
+ case FBIOCOPYAREA:
+ case FBIOFILLRECT:
arg = (unsigned long) compat_ptr(arg);
case FBIOBLANK:
ret = do_fb_ioctl(info, cmd, arg);
Unfortunately, it would not be as easy to add an FBIOIMAGE, which sounds
equally useful.
Arnd <><
next prev parent reply other threads:[~2009-07-13 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 15:17 [PATCH 0/2] fbdev: add fillrect and copyarea ioctls Ali Gholami Rudi
2009-07-13 15:17 ` Ali Gholami Rudi
2009-07-13 15:18 ` [PATCH 1/2] fbdev: add FBIOFILLRECT ioctl Ali Gholami Rudi
2009-07-13 15:20 ` [PATCH 2/2] fbdev: add FBIOCOPYAREA ioctl Ali Gholami Rudi
2009-07-13 15:40 ` [PATCH 0/2] fbdev: add fillrect and copyarea ioctls Arjan van de Ven
2009-07-13 16:25 ` Ali Gholami Rudi
2009-07-14 0:46 ` Dave Airlie
2009-07-14 3:43 ` Ali Gholami Rudi
2009-07-14 3:56 ` Dave Airlie
2009-07-14 9:47 ` Stelios Xanthakis
2009-07-13 16:35 ` Greg KH
2009-07-13 18:53 ` Arnd Bergmann [this message]
2009-07-13 19:52 ` Ali Gholami Rudi
2009-07-13 20:08 ` Ali Gholami Rudi
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=200907132053.13032.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=ali@rudi.ir \
--cc=gregkh@suse.de \
--cc=krzysztof.h1@wp.pl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=righi.andrea@gmail.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.