Re: [Lcd4linux-devel] Re: lcd4linux Noritake GUI128X32-311 - I got it working !

[Michael R. <re...@eu...>]

Hi Julien,

> I just want to tell you that I finally got my Noritake GU128x32-311
> working !
Well, that's great news!

> It is used as a text-mode display by now, even if it's a graphical 
> display (The display itself has 2 modes: one text and one graphic). 
> The problem with the graphic mode are, first, I'm worried about the 
> bandwidth needed on the parallel port to refresh all the display, and
> also, the microcontroller uses a very very weird way to pack the 
> data, and I could not find (yet) an efficient way to do it in C.
Could you send mo a description of the packed format?
There#s no need to worry about bandwidth issues, lcd4linux uses a very
sophisticated double-buffering, so the data transfers are reduced to a
minimum.

> Also, I did not put the "bars" widget support on this version, I will
> do it quickly through.
Don't care about it too much. As it's a graphical display, we should use
it's graphical mode only, and the bar rendering for graphic LCD's is
ready to use.

> - There is no TSC inside the MediaGX processor : Linux rely on a less
>  accurate timer, and it is sensitive to the load of the machine. (I
> measured that with an oscilloscope)
That's not that good, but it should not matter: just include some
reserve in your timing values.

> The only think that make me hesitate is that I don't know how to 
> *exactly* modify these #%!$#!@ autoconf/automake files in the CVS, to
>  avoid messing up everything.

> Michael, would it be possible for you to update the README.driver to 
> explain that as much as you can ? I don't want to mess up the 
> repository. Thanks !
Hmm... as this is quite complicated stuff, I don't see too much sense in
trying to document that. Could you send me a patch (cvs -z9 diff -u) and
I'll integrate it into the autojunk stuff.

> Next projects in the pipeline : - A driver for a SED1335 on USB
> display
Great!

> - A driver for a framebuffer display, because I want to map any 
> graphical display on a framebuffer, if the bandwidth to the display
> is sufficent.
Well, that's already done. drv_generic_graphic.c Take a look at the
T6963 driver, it uses this interface. It's that easy... you only have to
write sort of a 'blit' function, the generic graphic driver takes care
of the rest.


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781