Dear Phil,

First of all, the reason I did get nothing with was that the colorbar masked 
the image below.
After having disabled the colorbar the linux pinguin appeared on the top-left 
corner of the blue screen.
Then, I sent again the command

/# cp image /dev/fb/0

and something very confusing was displayed, like an incomplete version of the 
true image, compressed in the upper half of the panel.
Then, following your suggestion I get

/# fbset -fb /dev/fb/0

mode "720x480-29"
    # D: 5.556 MHz, H: 7.234 kHz, V: 29.406 Hz
    geometry 720 480 720 960 16
    timings 180000 40 4 8 2 4 2
    laced true
    rgba 5/11,6/5,5/0,0/0
endmode

Instead, what I really need is something like this

D: 6.75 MHz
H: 16.544 kHz
V: 63.145 Hz
geometry: 320 240
bits per pixel: 16
progressive
rgb656

So, I tryed to configure the video format in this way:

/# fbset -fb /dev/fb/0 -xres 320 -vxres 320
/# fbset -fb /dev/fb/0 -yres 240 -vyres 240
/# fbset -fb /dev/fb/0 -depth 16
/# fbset -fb /dev/fb/0 -pixclock 148148
/# fbset -fb /dev/fb/0 -left 68
/# fbset -fb /dev/fb/0 -right 20
/# fbset -fb /dev/fb/0 -upper 18
/# fbset -fb /dev/fb/0 -lower 4
/# fbset -fb /dev/fb/0 -hslen 0
/# fbset -fb /dev/fb/0 -vslen 0
/# fbset -fb /dev/fb/0 -laced false

And write out the image

/# cp image /dev/fb/0

After that I get info again:

/# fbset -fb /dev/fb/0 -i

mode "320x240-63"
    # D: 6.750 MHz, H: 16.544 kHz, V: 63.146 Hz
    geometry 320 240 320 240 16
    timings 148148 68 20 18 4 0 0
    nonstd 1
    rgba 5/11,6/5,5/0,0/0
endmode

Frame buffer device information:
    Name        : dm_osd0_fb
    Address     : 0x87600000
    Size        : 1658880
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 640
    MMIO Address: 0xfec72600
    MMIO Size   : 384
    Accelerator : No

Now the image is more readable, but still compressed in the top half of the 
screen, and with innatural colours (yellow instead of blue)

Any idea?

Regards

Gabriele


Da: Phil Quiney [mailto:[EMAIL PROTECTED]
Inviato: giovedì 23 ottobre 2008 14.00
A: Gabriele Filosofi; [email protected]
Oggetto: RE: dm644x - fbdev in kernel 2.6.25-davinci1

Hi Gabriele,

Can you check with 'fbset' what size the frame buffer is set to..

Something like 'fbset -fb /dev/fb/0'

If it is not 320x480 then you may find it will work if you use fbset to set the 
x & y resolution to match your LCD - I can't remember what the parameters are, 
possibly -xres/-yres (and also there is a -vxres/-vyres for a virtual size). I 
would set both xres and vxres to 320 and yres and vyres to 240 to start with.

You should be able to cat any old file to /dev/fb/0 and something appear on the 
display, /bin/busybox is what I use - it is quite colourful ;-)

Regards

Phil Q


Phil Quiney, Principal Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com<http://www.trinityconvergence.com/>


________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gabriele Filosofi
Sent: 23 October 2008 11:02
To: [email protected]
Subject: dm644x - fbdev in kernel 2.6.25-davinci1
Hi,

By modifying some VPBE registers I was able to display the colorbar on my QVGA 
LCD, so the hardware setup is ok.

Now I have an RGB656 image that is 320x240. What would be the best way to get 
it statically onto the screen?

By copying (cp image /dev/fb/0) or cutting (cat image > /dev/fb/0) I get 
nothing coming out of the display.
Is it not the fb stuff ready to be used in git kernel 2.6.25-davinci1? Is there 
anything I need to do?

Should I write a program that opens up the OSD0 and then set the OSD dimensions 
to 320x240 and then write the image file directly to /dev/fb/0?

kindly help me to come out from this problem.

Thanks and regards,

Gabriele


_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to