From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bhaskar <abc.bhaskar@gmail.com>
Cc: Linux-fbdev-devel@lists.sourceforge.net
Subject: Re: FramBuffer for ep9310 ARM Board
Date: Tue, 8 Apr 2008 09:28:08 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804080927400.20606@anakin> (raw)
In-Reply-To: <f63322490804072316g447cf528m5bd402f1b8f77645@mail.gmail.com>
On Tue, 8 Apr 2008, Bhaskar wrote:
> I need to modify modify Frame Buffer for ep9310 ARM board. The
> original frame buffer was provided by Cirrus Logic. For the debugging
> purpose, I introduced trace messages in frame buffer operation
> functions like imageblit, fillrect, etc.
>
> These messages appear only during Linux boot up and shutdown. When I
> move the window, none of the trace messages from the frame buffer
> appears. The Xserver used is XOrg-6.9
The in-kernel frame buffer operation functions like imageblit, fillrect,
etc. are not used from userspace. X does all drawing itself.
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 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-08 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 6:16 FramBuffer for ep9310 ARM Board Bhaskar
2008-04-08 7:28 ` Geert Uytterhoeven [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=Pine.LNX.4.64.0804080927400.20606@anakin \
--to=geert@linux-m68k.org \
--cc=Linux-fbdev-devel@lists.sourceforge.net \
--cc=abc.bhaskar@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