paul- wrote:
> I don't normally do this..... But does this handle what you need.
>
> 29111
>
> Also, let me know when your ready, I think we can handle the rest of the
> scripting in an extension.
>
> Paul
I note that physical and virtual geometry*, plus display depth, can all
be discovered by the fbset command:
Code:
--------------------
tc@piCorePlayer:~$ fbset -fb /dev/fb1 -s
mode "240x240-0"
# D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
geometry 240 240 240 240 16
timings 0 0 0 0 0 0 0
accel false
rgba 5/11,6/5,5/0,0/0
endmode
--------------------
So is the purpose of the Width, Height and Frame Depth parameters in the
interface above to allow these to be overridden? If not, is there a case
for making those read-only boxes that are populated when a framebuffer
device is selected (from a drop-down list perhaps)?
*The geometry parameters will match to whatever are the values of
framebuffer_width and framebuffer_height in config.txt. If those
parameters aren't set, then fbset seems to report the physical geometry.
In testing this I discovered that the framebuffer_width and
framebuffer_height parameters in config.txt are redundant if they are
simply set to match the physical geometry, so that's another step that
can be removed from my earlier list of instructions!
------------------------------------------------------------------------
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread: http://forums.slimdevices.com/showthread.php?t=111502
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
