Hi,
Is it possible to enable the second LCD on a blaze device using on of the pre-built android binaries? (i.e. without the need to modify and compile the source code)
Thanks a lot in advance,
Alireza
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
Is it possible to enable the second LCD on a blaze device using on of the pre-built android binaries? (i.e. without the need to modify and compile the source code)
Thanks a lot in advance,
Alireza
Hi Alireza,
Could you please let us know which software android release you are using to enable the second LCD?
Thanks & Best Regards,
Venkat
Hi Venkat,
I actually intend to use the latest ICS pre-built binary for blaze (i.e. http://omappedia.org/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes).
Thanks a lot,
Alireza
Hi Alireza,
What does it output when you execute the following sysfs commands after booting the device with pre-built binaries of 4AI.1.7 ICS release.
cat /sys/devices/platform/omapdss/display0/*
cat /sys/devices/platform/omapdss/display1/*
cat /sys/devices/platform/omapdss/display2/*
cat /sys/devices/platform/omapdss/display3/*
Thanks & Best Regards,
Venkat
Hi Venkat,
Below please find the output:
1- cat /sys/devices/platform/omapdss/display0/*
/sys/devices/platform/omapdss/di[91238.733795] omapdss DSI error: RX fifo empty when trying to read.
splay0/backlight[91238.741973] omapdss DSI error: dsi_vc_dcs_read(ch 0, cmd 0xda) failed
: invalid length[91238.751281] omapdss DSI error: rx fifo not empty when sending BTA, dumping data:
off ui still-i[91238.759338] omapdss DSI error: rawval 0x3b00e321
mage moving-imag[91238.765960] omapdss DSI error: DCS short response, 1 byte: 0xe3
e
off
/sys/dev[91238.773437] omapdss DSI error: RX fifo empty when trying to read.
ices/platform/om[91238.781341] omapdss DSI error: dsi_vc_dcs_read(ch 0, cmd 0x05) failed
apdss/display0/driver: invalid length
1
0
/sys/devices/platform/omapdss/display0/hw_revision: invalid length
0
lcd
/sys/devices/platform/omapdss/display0/num_dsi_errors: invalid length
/sys/devices/platform/omapdss/display0/power: invalid length
0
/sys/devices/platform/omapdss/display0/subsystem: invalid length
1
0,864/0/0/0,480/0/0/0
DRIVER=taal
0
0
2
/sys/devices/platform/omapdss/display0/wss: invalid length
2- cat /sys/devices/platform/omapdss/display1/*
0
/sys/devices/platform/omapdss/display1/driver: invalid length
0
/sys/devices/platform/omapdss/display1/mirror: invalid length
hdmi
/sys/devices/platform/omapdss/display1/power: invalid length
/sys/devices/platform/omapdss/display1/rotate: invalid length
0
frame_packing
/sys/devices/platform/omapdss/display1/subsystem: invalid length
0
0,640/0/0/0,480/0/0/0
DRIVER=hdmi_panel
1
/sys/devices/platform/omapdss/display1/wss: invalid length
3- cat /sys/devices/platform/omapdss/display2/*
/sys/devices/platform/omapdss/display2/*: No such file or directory
4- cat /sys/devices/platform/omapdss/display3/*
/sys/devices/platform/omapdss/display3/*: No such file or directory
Unfortunately it is not possible to use the second LCD on blaze with the ICS releases. I understand it is reenabled in JellyBean. You cannot even compile it in because there are no patches available for this. The second display panel is not defined in the 4430sdp board file. The hardware for DSI2 is not exposed within the kernel api's. It use is unsupported in ICS at present.
Hi Matthew,
Thanks a lot for your reply. As you mentioned the 2nd LCD is enabled in Jelly Bean release. Therefore, if I just compile the source code (I believe there is no prebuilt binary available for Blaze Mobile platform at the moment) the second LCD should work. Is that correct? In not, what changed do I need to make in order to enable the 2nd LCD on a Jelly Bean release.
Cheers,
Alireza
You should not have to make any changes that I am aware of for LCD2 on JB.