Thread
:
The N9/N950 Kernel Upstreaming Force
View Single Post
filip.pz
2015-10-22 , 16:53
Posts: 108 | Thanked: 579 times | Joined on Feb 2013 @ Požega, Croatia
#
75
Originally Posted by
marmistrz
Does it mean that the display driver works on N9 (pyrenees) but not on N950 (himalaya)?
Probably not. It needs same power supplies as does pyrenees, but DSI bus HS clocks are different N9 = 210.24 MHz (
https://github.com/filippz/kernel-ad...-rm680.c#L1907
) vs N950 = 256.32 MHz (
https://github.com/filippz/kernel-ad...-rm680.c#L1953
) - same goes for LP clocks. Other than that himalaya seems to be more like taal display (as pyrenees is OLED based) which is supported in mainline.
Still, I suggest working on 3.5 which is know to boot N950 with working display/touchscreen. When (if?) I get USB to work on mainline we'll be able to ssh into N9/N950 and use dmesg to see what's going on instead of serial cable. I suppose that's our best bet to make working display driver for N950.
I wonder if we could make use of ubiboot to load ubiboot again just on mainline kernel instead of some other OS (Nemo, SFOS, Debian) - as it just has what we need at this stage (watchdog kicking, display+touchscreen, usb networking + telnet/ssh). Other OS-es are quite "heavy" now and expect existance of WiFi, CMT, Audio, ALS/PS, BME.... Just an idea if someone would consider testing it
Quote & Reply
|
The Following 5 Users Say Thank You to filip.pz For This Useful Post:
Halftux
,
hrbani
,
juiceme
,
marmistrz
,
peterleinchen
filip.pz
View Public Profile
Send a private message to filip.pz
Find all posts by filip.pz