nanogui: screen subdriver problems
Subject:
Re: screen subdriver problems
From:
"Jordan Crouse" ####@####.####
Date:
5 Aug 2005 15:04:37 +0100
Message-Id: <20050805140539.GH6451@cosmic.amd.com>
On 04/08/05 15:28 -0700, Srinivasa Mylarappa wrote:
> My LCD controller does not allow direct access to video memory. So I have to
> flush the contentes of the frame buffer to LCD controller. When should I flush
> this if I'm running nano-X, nanowm,applications?
I could have sworn we had a sync() function for the display drivers, but we
don't. IMHO thats a fairly important piece to be missing.
My advice is to add a sync hook to the driver structure. Of course, most of
the drivers won't have a need for a sync function, so no drastic changes would
be needed in the driver/ directory, as we could just leave those null.
Then, we should define a macro like so:
#define NXSYNC(psd) \
do { if ((psd)->Sync != NULL) psd->Sync(); } while(0)
(Or whatever - that might not compile.. :D)
Anyway, the point is that the NXSYNC() macro should then go at the bottom of
any drawing functions to flush the hardware as needed. I think the process
of adding NXSYNC() calls can be organic (in that we add them as we need
them), unless anybody has the initative to add them everywhere at once.
Comments?
Jordan
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
