From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: vesafb
Date: Thu, 08 Jun 2006 08:32:49 +0800 [thread overview]
Message-ID: <44877031.80409@gmail.com> (raw)
In-Reply-To: <bb9a78950606051102s514075aar7924d05756ccd3c1@mail.gmail.com>
Nathan King wrote:
> Hey folks,
>
> I'm trying to get a feel for how all this works as I get ready to really
> start monkeying with the driver, so I liberally sprinkled some printk's
> around vesafb.c and cfb_fillrect.c and recompiled. However I only ever
> get messages from three of the vesafb.c functions, all on bootup, and
> none from cfb_fillrect.c. I know doing all those messages will slow down
> my system(or they would if they worked right) but I'm just trying to
> figure out what files control what.
>
> So my question is, which files are responsible for all these constant
> fillrect and bitblt operations, and can they monkeyed with to generate
> kernel or other messages?
fillrect is called by ops->fill and ops->clear_margins. The first one
should be called when scrolling the screen, while the second will be
called if xres is not divisible by the fontwidth or yres is not divisible
by the fontheight.
Tony
next prev parent reply other threads:[~2006-06-08 0:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 18:02 vesafb Nathan King
2006-06-08 0:32 ` Antonino A. Daplas [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-30 20:54 vesafb ron minnich
2007-04-30 21:52 ` vesafb Ian Pratt
2007-05-01 0:13 ` vesafb ron minnich
2007-05-07 13:29 vesafb Jayant Mangalampalli
2007-05-07 19:57 ` vesafb ron minnich
2007-05-07 20:14 ` vesafb Ian Pratt
2007-05-08 3:14 ` vesafb Kaushik Barde
2007-05-08 7:22 ` vesafb Jan Beulich
2007-05-08 7:40 ` vesafb Keir Fraser
2007-05-08 7:50 ` vesafb Jan Beulich
2007-05-08 8:00 ` vesafb Keir Fraser
2007-05-08 9:56 ` vesafb Jan Beulich
2007-05-08 10:38 ` vesafb Keir Fraser
2007-05-08 19:20 ` vesafb Kaushik Barde
2007-05-08 20:06 ` vesafb Keir Fraser
2007-05-08 20:47 ` vesafb Kaushik Barde
2007-05-08 21:34 ` vesafb Keir Fraser
2007-05-08 21:43 ` vesafb Kaushik Barde
2007-05-09 7:48 ` vesafb Jan Beulich
2007-05-09 8:14 ` vesafb Keir Fraser
2007-05-08 8:49 vesafb Ian Pratt
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=44877031.80409@gmail.com \
--to=adaplas@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.