**** BEGIN LOGGING AT Thu May 24 02:59:58 2012
May 24 06:30:59 <snkt> can I able to knew .... why in ARM based embedded system we have to give hardcoded LCD Screen resolution parameters? why the drivers detects the possible screen resolution supported by an LCD ?
May 24 06:38:19 <PaulFertser> snkt: depends on the hardware used to drive LCD of course.
May 24 06:38:53 <snkt> PaulFertser, but if I have to set parameters for different resolution (for e.g. 1024x768) ... how should I calculate this parameter?
May 24 06:40:09 <snkt> PaulFertser, this is the struct from which it take the resolution.... http://pastebin.mozilla.org/1649122
May 24 06:41:53 <PaulFertser> snkt: "struct display_module_info" looks to be driver-specific and not mainline.
May 24 06:44:52 <PaulFertser> snkt: btw, the current trend is to supply such information with device-tree which can be passed from the bootloader, and hence not hardcoded.
May 24 06:45:24 <snkt> PaulFertser, ya I knew... but it takes the values from this structure... this is my actually lcd.c file placed in arch/arm/mach-cl7700/lcd.c .... http://pastebin.mozilla.org/1649123
May 24 06:48:57 <PaulFertser> snkt: so, what's your question? You need to understand the sources of that your private video-driver to know how to tweak its parameters.
May 24 06:49:13 <snkt> PaulFertser, ya...
May 24 06:49:55 <snkt> PaulFertser, If I have to calculate for 1024x768 .... how can I set this values?
May 24 06:54:02 <PaulFertser> snkt: to understand the basics of the video-timings read http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/
**** ENDING LOGGING AT Fri May 25 02:59:59 2012