Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 1 day, 3 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 3 days ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 3 days, 20 hrs ago - more...
 |
|
2015-10-05
, 05:36
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#52
|
Believe it or not... this is actually good:
https://www.dropbox.com/s/fww96kfiaa..._2240.JPG?dl=0
Took me huge amount of time to get OMAP DSS to even talk to display panel, as it seems that DSS kernel drivers aren't doing a good job when bootloader (MOSLO, ubiboot...) configures DSS before boot.
A few things remain to be done:
As mentioned earlier, log now show IRQ problem (http://pastie.org/10460434) which seem to be related to TE IRQ, and hopefully resetting whole DSS before configuring it will fix this.
Also, I wasn't able to match LP clock speed to the one in older kernels which may be of some importance. Current DSS drivers configure necessary dividers for specified clocks themselves as opposed to old ones where dividers were set trough manual configuration (and older DSI drivers were rigged to optionally use alternate clock source making it easier to match desired speeds). Since I don't have any datasheet of N9/N950 displays (they seem to be manufactured by Samsung Display and AU Optronics respectfully) I can't really tell what clock speeds are really supported.
https://www.dropbox.com/s/fww96kfiaa..._2240.JPG?dl=0
Took me huge amount of time to get OMAP DSS to even talk to display panel, as it seems that DSS kernel drivers aren't doing a good job when bootloader (MOSLO, ubiboot...) configures DSS before boot.
A few things remain to be done:
- reset other parts of DSS subsytem (now I'm just resseting DSI) and that might prevent trouble with TE (Tear Elimination) IRQ
- add support for multiple displays in panel-dsi-cm.c (for now I've just replaced taal specific parts with pyrenees ones)
- entries in Harmattan kernel suggest that certain pyrenees panels don't handle properly reading from it's registers in HS (High Speed) mode - drop to LP (Low Power) mode before reading, and revert to HS after to be safe
- add support for N950 himalaya panel
As mentioned earlier, log now show IRQ problem (http://pastie.org/10460434) which seem to be related to TE IRQ, and hopefully resetting whole DSS before configuring it will fix this.
Also, I wasn't able to match LP clock speed to the one in older kernels which may be of some importance. Current DSS drivers configure necessary dividers for specified clocks themselves as opposed to old ones where dividers were set trough manual configuration (and older DSI drivers were rigged to optionally use alternate clock source making it easier to match desired speeds). Since I don't have any datasheet of N9/N950 displays (they seem to be manufactured by Samsung Display and AU Optronics respectfully) I can't really tell what clock speeds are really supported.
|
|
2015-10-11
, 16:22
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#53
|
We have working framebuffer now:
https://www.dropbox.com/s/3hfp0rjf0m..._6403.JPG?dl=0
I couldn't get rid of omapdss DSI error: Framedone not received for 250ms! when declaring screen to be 480x864. I had to swap x and y resolutions, and apply rotation by 90° (on the panel itself). Also, visible area is 480x854 not 480x864, so that was also added to panel driver. Swapping x and y can be eventually corrected trough framebuffer rotation (/sys/devices/platform/omapdss/display0/rotate) and by using fbset (this is what we use on SFOS, but Nemo has a hidden ace in his sleeve: https://github.com/nemomobile-ux/gla...c/main.cpp#L41) If necessary we could use ubiboot boot args to set these, hiding this stuff form userspace altogether.
By looking at the code in 2.6 kernel, there are a lot of hacks depending on panel revision/manufacturer (pyrenees is manufactured by either Samsung Mobile Display or LG Display). Since my panel revision (fe.91.96) seem to be unaffected by most (all?) of them, adding those bits will be done at a later time since I can't really test if they make any difference. It's possible that those panels didn't make it into the wild (or at least some of them), so we might actually be OK. If someone has different rev then mine, please post so (dmesg | grep -i pyrenees)
Next in line are PowerVR drivers and touchscreen...
Last edited by filip.pz; 2015-10-13 at 10:22.
https://www.dropbox.com/s/3hfp0rjf0m..._6403.JPG?dl=0
I couldn't get rid of omapdss DSI error: Framedone not received for 250ms! when declaring screen to be 480x864. I had to swap x and y resolutions, and apply rotation by 90° (on the panel itself). Also, visible area is 480x854 not 480x864, so that was also added to panel driver. Swapping x and y can be eventually corrected trough framebuffer rotation (/sys/devices/platform/omapdss/display0/rotate) and by using fbset (this is what we use on SFOS, but Nemo has a hidden ace in his sleeve: https://github.com/nemomobile-ux/gla...c/main.cpp#L41) If necessary we could use ubiboot boot args to set these, hiding this stuff form userspace altogether.
By looking at the code in 2.6 kernel, there are a lot of hacks depending on panel revision/manufacturer (pyrenees is manufactured by either Samsung Mobile Display or LG Display). Since my panel revision (fe.91.96) seem to be unaffected by most (all?) of them, adding those bits will be done at a later time since I can't really test if they make any difference. It's possible that those panels didn't make it into the wild (or at least some of them), so we might actually be OK. If someone has different rev then mine, please post so (dmesg | grep -i pyrenees)
Next in line are PowerVR drivers and touchscreen...
Last edited by filip.pz; 2015-10-13 at 10:22.
 |
|
2015-10-11
, 19:04
|
|
Posts: 4,117 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#54
|
Mine is "" 
do not get anything on HW rev1601
do not get anything on HW rev1601
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
|
|
2015-10-12
, 05:02
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#55
|
Originally Posted by peterleinchen
Just tried it on my N9:
Mine is ""
do not get anything on HW rev1601
Code:
~ $ dmesg | grep -i pyrenees [ 0.276153] panel-nokia-dsi display0: pyrenees panel revision fe.91.96 [ 10.529815] atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin
You can try rebooting before those commands (I'm unsure if kernel log overflows in time...)
| The Following 6 Users Say Thank You to filip.pz For This Useful Post: | ||
|
|
2015-10-12
, 06:51
|
|
Posts: 4,117 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#56
|
Originally Posted by filip.pz
Yep, it does:
You can try rebooting before those commands (I'm unsure if kernel log overflows in time...)
Code:
~ $ dmesg |grep -i pyr panel-nokia-dsi display0: pyrenees panel revision fe.91.96 atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin ~ $ dmesg |grep -i atmel input: Atmel mXT Touchscreen as /devices/platform/i2c_omap.2/i2c-2/2-004b/input/input3 atmel_mxt: Atmel mXT Touchscreen v1.6 (0x29b82f) var:0x1 bld:0xab atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature
|
|
2015-10-12
, 15:30
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#58
|
Originally Posted by peterleinchen
Ah the infamous 1601 raises its head again!
Mine is ""
do not get anything on HW rev1601
| The Following 3 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2015-10-15
, 17:44
|
|
Posts: 204 |
Thanked: 443 times |
Joined on Jul 2012
@ Germany - Potsdam
|
#59
|
hardware revision 1501 (black 64GB)
Code:
dmesg | grep -i pyr panel-nokia-dsi display0: pyrenees panel revision fe.91.96 atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin dmesg | grep -i atmel input: Atmel mXT Touchscreen as /devices/platform/i2c_omap.2/i2c-2/2-004b/input/input3 atmel_mxt: Atmel mXT Touchscreen v1.6 (0x29b82f) var:0x1 bld:0xab atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin
|
|
2015-10-15
, 18:31
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#60
|
On N950
Last edited by marmistrz; 2015-10-15 at 18:47.
Code:
$dmesg | grep panel [ 0.307312] panel-nokia-dsi display0: himalaya panel revision 38.95.8a $ dmesg | grep atmel [ 0.236114] atmel_mxt: Atmel mXT Touchscreen v1.1 (0x12a9d8) var:0xc bld:0xac [ 11.132659] atmel_mxt 2-004b: firmware: requesting RM-680_Himalaya_AUO_V1_1.bin
__________________
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
If you want to support my work, you can donate by PayPal or Flattr
Projects no longer actively developed: here
Last edited by marmistrz; 2015-10-15 at 18:47.
To me it seems your kernel was not found at all, so wrong config?
(as when second kernel was loaded and execution handed over there should be no such message)
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!
Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257
editsignature, http://talk.maemo.org/profile.php?do=editsignature