linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zajicek <santiago@crfreenet.org>
To: "René Kolařík" <rene.kolarik@seznam.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: framebuffer general questions
Date: Mon, 16 Nov 2009 01:06:20 +0100	[thread overview]
Message-ID: <20091116000619.GA27314@localhost> (raw)
In-Reply-To: <938.2731-16809-9592867-1258327686@seznam.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1662 bytes --]

On Mon, Nov 16, 2009 at 12:28:06AM +0100, René Kolařík wrote:
> Thanks for your answer, but it implied some other questions :-)
> 

> You said, that accelerated functions are called from console - so
> programs wich are drawing directly to FB (like QT embedded in my case)
> have no profit from them? Or do they?

They have no profit from them.

> What is actually the best technique of using FB (for achieving the
> best performance) - should i malloc a piece of RAM, draw to it and then
> memmove it to FB mapped address as a whole frame or draw directly to FB?
> Or it doesnt matter?

Depends on hardware and style of drawing. Dedicated graphics cards have
slower write (compared to main memory speed) and very slow read, so you
really don't want to do alpha-blending directly on mmaped framebuffer.

> When i greped through drivers sources i was expecting that accelerated
> drivers will use mmap only for registers and that the imageblit function
> would be implemented as some DMA fetching from system memory. But i was
> wrong, there are still mmaps to video memory. So i want to ask, if that
> idea is completely wrong and why drivers of GPUs use mmap to video mem,
> when they have DMA controller.

You mean fbdev drivers? FBdev API is designed to just allow mmap
framebuffer to userspace. It is not a good way to use modern GPU with
DMA transfers. Perhaps you could use DRI for that.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 354 bytes --]

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

      reply	other threads:[~2009-11-16  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 14:11 framebuffer general questions René Kolařík
2009-11-13 20:08 ` Ondrej Zajicek
2009-11-15 23:28   ` René Kolařík
2009-11-16  0:06     ` Ondrej Zajicek [this message]

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=20091116000619.GA27314@localhost \
    --to=santiago@crfreenet.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rene.kolarik@seznam.cz \
    /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;
as well as URLs for NNTP newsgroup(s).