nanogui: Confused with SCREENDEVICE
Subject:
Re: [nanogui] Confused with SCREENDEVICE
From:
"Robbie" ####@####.####
Date:
31 Dec 2005 04:25:18 +0000
Message-Id: <20051231042514.038BB8A1B9@xprdmxin.myway.com>
You're correct. I did figure out what I was missing after I sent the email. I guessed I "spoke" too fast. Thanks though.
There is one thing that's bugging me and although I not sitting infont of the source, I think the names are pretty close if ot exact. What's the difference between RGB2PIXEL and COLORVAL2PIXELVAL? I could see where RGB2PIXELVAL comes in, but COLORVAL2PIXELVAL? They seem to be saying the same thing to me.
--- On Fri 12/30, Greg Haerr < ####@####.#### > wrote:
From: Greg Haerr [mailto: ####@####.####
To: ####@####.#### ####@####.####
Date: Fri, 30 Dec 2005 17:17:53 -0800
Subject: Re: [nanogui] Confused with SCREENDEVICE
> I have a bit of confusion with the SCREENDEVICE scrdev.
> The file fb.c describes a SCREENDEVICE scrdev with several attributes,
fb_mapmemgc for example. However, there is access to a scrdev.xvirtres but
xvirtres is not in scrdev.??
That's incorrect, xvirtres is defined in the SCREENDEVICE structure,
see include/device.h.
> Am I missing something here? Where is fb_mapmemgc calles?
The mapmemgc entry is typically called on driver init. Grep for
calls to MapMemGC.
>
> Also, subdriver functions,where are they called? Say I use fblinear16,
when or/and where are its functions called? Could someone help me clear this
up?
The subdriver functions are called from the engine level, DrawPixel,
DrawLine, etc. They are mapped to the subdriver entry points
with similar names.
Read the Architecture doc for more details.
Regards,
Greg
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
