* vesafb
@ 2006-06-05 18:02 Nathan King
2006-06-08 0:32 ` vesafb Antonino A. Daplas
0 siblings, 1 reply; 2+ messages in thread
From: Nathan King @ 2006-06-05 18:02 UTC (permalink / raw)
To: linux-fbdev-devel
[-- Attachment #1.1: Type: text/plain, Size: 719 bytes --]
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?
Using 2.6.16 with fedora core 5 and the VESA driver.
Many thanks,
Nathan
[-- Attachment #1.2: Type: text/html, Size: 754 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: vesafb
2006-06-05 18:02 vesafb Nathan King
@ 2006-06-08 0:32 ` Antonino A. Daplas
0 siblings, 0 replies; 2+ messages in thread
From: Antonino A. Daplas @ 2006-06-08 0:32 UTC (permalink / raw)
To: linux-fbdev-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-06-08 0:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-05 18:02 vesafb Nathan King
2006-06-08 0:32 ` vesafb Antonino A. Daplas
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).