pollux_set
(c) notaz, 2009
This is a simple tool for setting various timings on Wiz, which can be used
standalone (from launcher scripts, for example) or compiled into your program
if you are writing one. It accepts a string which contains timing values, for
example:
./pollux_set 'lcd_timings=397,1,37,277,341,0,17,337.lcd_clkdiv0=9'
currently accepted arguments are:
lcd_timings=<htotal,hswidth,hastart,haend,vtotal,vswidth,vastart,vaend>
ram_timings=<CAS,tRC,tRAS,tWR,tMRD,tRP,tRCD>
dpc_clkdiv0=<pixel_clock_divider>
cpuclk=<MHZ>
If you use this in your program, you can keep that string in config file,
environment variable, etc, and pass it to this code. The idea is to keep it
in user editable form in case it doesn't work for everyone or somebody prefers
something different.
This program is released under BSD license, see the included pollux_set.c
for license text.
(c) notaz, 2009
This is a simple tool for setting various timings on Wiz, which can be used
standalone (from launcher scripts, for example) or compiled into your program
if you are writing one. It accepts a string which contains timing values, for
example:
./pollux_set 'lcd_timings=397,1,37,277,341,0,17,337.lcd_clkdiv0=9'
currently accepted arguments are:
lcd_timings=<htotal,hswidth,hastart,haend,vtotal,vswidth,vastart,vaend>
ram_timings=<CAS,tRC,tRAS,tWR,tMRD,tRP,tRCD>
dpc_clkdiv0=<pixel_clock_divider>
cpuclk=<MHZ>
If you use this in your program, you can keep that string in config file,
environment variable, etc, and pass it to this code. The idea is to keep it
in user editable form in case it doesn't work for everyone or somebody prefers
something different.
This program is released under BSD license, see the included pollux_set.c
for license text.