[#4563] jpegview cannot work on framebuffer device other than 16BPP
Submitted By: Yi Li
Open Date
2008-10-23 00:46:59 Close Date
2009-01-08 09:57:03
Priority:
Medium Assignee:
Graf Yang
Status:
Closed Fixed In Release:
N/A
Found In Release:
N/A Release:
trunk
Category:
N/A Board:
N/A
Processor:
N/A Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Fixed
Uboot version or rev.:
Toolchain version or rev.:
App binary format:
N/A
Summary: jpegview cannot work on framebuffer device other than 16BPP
Details:
jpegview is hard coded to handle framebuffer device with 16BPP only (and the RGB format is fixed). It cannot work properly on LCD driver like bfin-t350mcqb on BF527-ezkit. Need to rewrite jpegview.
Follow-ups
--- Robin Getz 2008-10-23 07:41:25
Or Dump it - since there are alternatives (like
user/blkfin-apps/sdl-examples/vp-1.7) which do work on 16BPP displays.
?
-Robin
--- Mike Frysinger 2008-10-23 12:52:46
it's been merged upstream now ... it also has the advantage of only needing a
framebuffer and jpeg ...
--- Graf Yang 2008-11-18 05:10:33
The sdl example vp can show 16/24bits images on LCD, but it's R and B channel
are inverted. I'm checking it.
--- Mike Frysinger 2008-11-18 08:39:30
if the code assumes a certain RGB encoding, then it'll display incorrectly on
devices that are not the same (RGB / BGR). see bug #4646.
--- Graf Yang 2008-11-19 22:19:35
But other applications,like sdl-examples/fire, is always display OK.
I think it's a bug, maybe in SDL library.
--- Graf Yang 2008-11-19 23:59:58
I add a workaround to bfin_t350mcqb_fb_check_var(), let it restore the RGB's
offset and length, in case of user application changed these information. Now
the display is OK.
--- Graf Yang 2008-11-21 04:09:39
Now can close it.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
No Files Were Found