Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Ali Gholami Rudi <ali@rudi.ir>
To: Dave Airlie <airlied@gmail.com>
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 08:13:53 +0430	[thread overview]
Message-ID: <20090714034353.GA1280@lilem.mirepesht> (raw)
In-Reply-To: <21d7e9970907131746q4f1a34efw9d3e6efaa78aea34@mail.gmail.com>

Dave Airlie <airlied@gmail.com> wrote:
> On Tue, Jul 14, 2009 at 2:25 AM, Ali Gholami Rudi<ali@rudi.ir> wrote:
> > Arjan van de Ven <arjan@infradead.org> wrote:
> >> 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.

I see.  The line between user- and kernel-space for graphic applications
is very blurred to me :-)

> Not all hw can implement these usefully in the kernel, directfb

AFAICT, many major ones like intelfb, radeonfb and nv implement them and
those that can't, use a software implementation.  You mean they are
unreliable or that there is little performance improvement because of
the way those operations are implemented in the kernel?

> already does some
> things for this.

Sometime ago I did try running directfb on a radeon r300 and it failed.
I didn't try hard to see what's wrong but I got the impression that
userspace apps are not good at using the hardware directly.

	Ali

  reply	other threads:[~2009-07-14  3:43 UTC|newest]

Thread overview: 13+ 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: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 [this message]
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
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=20090714034353.GA1280@lilem.mirepesht \
    --to=ali@rudi.ir \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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