From: Dave Airlie <airlied@gmail.com>
To: Ali Gholami Rudi <ali@rudi.ir>
Cc: Arjan van de Ven <arjan@infradead.org>,
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>,
Greg Kroah-Hartman <gregkh@suse.de>,
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: Tue, 14 Jul 2009 10:46:12 +1000 [thread overview]
Message-ID: <21d7e9970907131746q4f1a34efw9d3e6efaa78aea34@mail.gmail.com> (raw)
In-Reply-To: <20090713162559.GA1279@lilem.mirepesht>
On Tue, Jul 14, 2009 at 2:25 AM, Ali Gholami Rudi<ali@rudi.ir> wrote:
> Arjan van de Ven <arjan@infradead.org> wrote:
>> On Mon, 13 Jul 2009 19:47:09 +0430
>> Ali Gholami Rudi <ali@rudi.ir> wrote:
>> > 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.
>> >
>>
>> can we turn this around, is there a reason to add them?
>> or in other words, how / where would these be used ?
>
> User-space programs that use framebuffer directly can use them. I was
> writing a simple framebuffer virtual terminal (using libfreetype for
> fonts; like fbterm); scrolling and painting boxes would be faster if
> there was someway of using hardware accelerated operations. I think
> other similar programs can benefit, too.
The general opinion is we should keep acceleration in userspace if at
all possible.
Not all hw can implement these usefully in the kernel, directfb
already does some
things for this.
Dave.
next prev parent reply other threads:[~2009-07-14 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-07-14 3:43 ` Ali Gholami Rudi
2009-07-14 3:56 ` Dave Airlie
2009-07-13 16:35 ` Greg KH
2009-07-13 18:53 ` Arnd Bergmann
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=21d7e9970907131746q4f1a34efw9d3e6efaa78aea34@mail.gmail.com \
--to=airlied@gmail.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=ali@rudi.ir \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®