QVGA Mode

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(New page: Information on getting into QVGA mode successfully === SHR === On SHR-unstable (as of the Sept 2009 builds) the following worked. Create two new scripts - I put these in /usr/local/bin...)
 
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Languages|QVGA Mode}}
 
Information on getting into QVGA mode successfully
 
Information on getting into QVGA mode successfully
  
 
=== SHR ===  
 
=== SHR ===  
  
On SHR-unstable (as of the Sept 2009 builds) the following worked.
+
On SHR-unstable (as of the july 2011 (openembedded)builds) the following worked.
  
 
Create two new scripts - I put these in /usr/local/bin, and added /usr/local/bin to my PATH in my .profile file - but you can put 'em where ever you like, as long as they are on your PATH, or you use the full path to invoke 'em.
 
Create two new scripts - I put these in /usr/local/bin, and added /usr/local/bin to my PATH in my .profile file - but you can put 'em where ever you like, as long as they are on your PATH, or you use the full path to invoke 'em.
Line 10: Line 11:
 
<pre>
 
<pre>
 
#!/bin/sh
 
#!/bin/sh
echo "qvga-normal" > /sys/bus/spi/devices/spi2.0/state
+
xrandr --dpi 143
 +
echo "qvga" > /sys/bus/spi/devices/spi2.0/resolution
 
xrandr -s 240x320
 
xrandr -s 240x320
fbset 240x320           
 
 
killall -HUP enlightenment
 
killall -HUP enlightenment
 
</pre>
 
</pre>
Line 19: Line 20:
 
<pre>
 
<pre>
 
#!/bin/sh
 
#!/bin/sh
echo "normal" > /sys/bus/spi/devices/spi2.0/state
+
xrandr --dpi 280
 +
echo "vga" > /sys/bus/spi/devices/spi2.0/resolution
 
xrandr -s 480x640
 
xrandr -s 480x640
 
killall -HUP enlightenment
 
killall -HUP enlightenment
 
</pre>
 
</pre>
  
and add to /etc/fb.modes
+
This usually creates a usable display
<pre>
+
mode "240x320"
+
      geometry 240 420 240 320 16
+
      timings 100000 8 88 2 2 8 2
+
      accel false
+
endmode
+
</pre>
+
 
+
This usually creates a usable display - although occasionally enlightnment get confused and crashes.
+
  
Unfortunately there's a problem with the touchscreen, so the upper quarter of the screen maps to the entire screen, so using this for anything real isn't possible.  Apparently this is fixed in the Xorg based X server, which should be available soon, so hopefully this will be resolved soon.
+
[[Category:SHR]]

Latest revision as of 16:19, 20 July 2011

Information on getting into QVGA mode successfully

[edit] SHR

On SHR-unstable (as of the july 2011 (openembedded)builds) the following worked.

Create two new scripts - I put these in /usr/local/bin, and added /usr/local/bin to my PATH in my .profile file - but you can put 'em where ever you like, as long as they are on your PATH, or you use the full path to invoke 'em.

qvga:

#!/bin/sh
xrandr --dpi 143
echo "qvga" > /sys/bus/spi/devices/spi2.0/resolution
xrandr -s 240x320
killall -HUP enlightenment

normal:

#!/bin/sh
xrandr --dpi 280
echo "vga" > /sys/bus/spi/devices/spi2.0/resolution
xrandr -s 480x640
killall -HUP enlightenment

This usually creates a usable display

Personal tools

Information on getting into QVGA mode successfully

SHR

On SHR-unstable (as of the Sept 2009 builds) the following worked.

Create two new scripts - I put these in /usr/local/bin, and added /usr/local/bin to my PATH in my .profile file - but you can put 'em where ever you like, as long as they are on your PATH, or you use the full path to invoke 'em.

qvga:

#!/bin/sh
echo "qvga-normal" > /sys/bus/spi/devices/spi2.0/state
xrandr -s 240x320
fbset 240x320             
killall -HUP enlightenment

normal:

#!/bin/sh
echo "normal" > /sys/bus/spi/devices/spi2.0/state
xrandr -s 480x640
killall -HUP enlightenment

and add to /etc/fb.modes

mode "240x320"
       geometry 240 420 240 320 16
       timings 100000 8 88 2 2 8 2
       accel false
endmode

This usually creates a usable display - although occasionally enlightnment get confused and crashes.

Unfortunately there's a problem with the touchscreen, so the upper quarter of the screen maps to the entire screen, so using this for anything real isn't possible. Apparently this is fixed in the Xorg based X server, which should be available soon, so hopefully this will be resolved soon.