linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jorge Marques Pelizzoni <jpeliz@icmc.usp.br>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: newbie: fb specs and indirect VRAM access
Date: Thu, 21 Aug 2008 14:54:19 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0808211453330.31396@anakin> (raw)
In-Reply-To: <34825.200.178.190.130.1219322627.squirrel@mail2.icmc.usp.br>

On Thu, 21 Aug 2008, Jorge Marques Pelizzoni wrote:
> A few days ago I sent the message below asking about framebuffer device
> documentation and explaining my specific situation. Nobody aswered and I
> wonder why. If those are not questions for this list, can someone please
> redirect me to the right forum?

I had hoped somebody else would find time to respond ;-)

> Jorge Marques Pelizzoni escreveu:
> > I am considering implementing a frame buffer device for a mobile platform
> > (LPC2400 on uCLinux) that, as far as I can tell, seems to lack one. Well,
> > I am a newbie to all things frame buffer-related (though familiar with
> > kernel/device module implementation) and would most appreciate it if you
> > could answer the following questions:
> >
> > 1 - are there documents specifying frame buffer devices and how
> > applications are expected to handle them (in short, their API)?

linux/Documentation/fb/framebuffer.txt
linux/include/linux/fb.h

> > 2 - my CPU cannot address "real" VRAM directly, all control being carried
> > out by means of a parallel interface. I gathered that an fb user is
> > expected to write to (virtual) VRAM directly via a pointer provided by the
> > driver and never notifies the driver of changes. Have you seen such a
> > set-up before and do you think these requirements can be reconciled? The
> > only way round this I can currently see is making the driver periodically
> > check the virtual VRAM for changes and transmit only changed parts. All in
> > all, a costly operation, as everything must be carried out by the same
> > CPU. Could whatever is used to implement mmap be called into play (without
> > whatever is used to implement msync)?

linux/Documentation/fb/deferred_io.txt

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

  reply	other threads:[~2008-08-21 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 20:31 newbie: fb specs and indirect VRAM access Jorge Marques Pelizzoni
2008-08-21 12:43 ` Jorge Marques Pelizzoni
2008-08-21 12:54   ` Geert Uytterhoeven [this message]
2008-08-21 13:09     ` Jaya Kumar
2008-08-21 13:21       ` Geert Uytterhoeven
2008-08-21 13:49         ` Jorge Marques Pelizzoni

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=Pine.LNX.4.64.0808211453330.31396@anakin \
    --to=geert@linux-m68k.org \
    --cc=jpeliz@icmc.usp.br \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).