Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 6 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 3 days, 7 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 23 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 21 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 3 hrs ago - more...
| The Following 5 Users Say Thank You to JanneN9 For This Useful Post: | ||
 |
|
2015-09-25
, 07:31
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#42
|
Originally Posted by JanneN9
I can send you defconfig and build scripts I used (PM me your e-mail for that), but at this point without working serial console you'll not be able to do much as there is no display/sound/led...
I would like to help, but I'm currently stuck - correct way of compilation is not clear.
I can compile mer-n9-2.6.32-latest-nokia-pr1.3 with Open Mode patch.
- but do I have correct xxx_defconfig is unknown
Is there something secret thing to be done, because I try new kernel with ubiboot (easier would be just flash new version)
- my version shut down without any evidence what went wrong
Janne
You might wait a few days for me to port pvr kernel modules from 3.5.3 and get the display running (hopefully)
|
|
2015-09-26
, 06:39
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#43
|
Progress update:
Yesterday I managed to update PVR kernel drivers to "something" that compiles with current kernel by removing the following:
However, to even try getting the display to work we still need the following:
In 3.5.3 that stuff was in the following files (list may not be complete):
Good news: display driver might be ready in https://github.com/torvalds/linux/bl...panel-dsi-cm.c (taal is mentioned there, probably needs tweaking for himalaya and pyrenees). Seems that there were plans for adding other display types into it, but were abandoned: https://github.com/torvalds/linux/co...096b825326d3e2
Bad news: I really don't know enough about this to be able to port these parts myself 
Any volunteers 
Last edited by filip.pz; 2015-10-09 at 09:54. Reason: fixed display code names
Yesterday I managed to update PVR kernel drivers to "something" that compiles with current kernel by removing the following:
- /proc entries as the code is not updated to use seq_file required in kernel >= 3.10
- notification between OMAP DSS display driver and PVR (this is not implemented in OMAP DSS)
- power management features (they are not implemented in kernel: https://github.com/torvalds/linux/bl...omap-pm-noop.c)
However, to even try getting the display to work we still need the following:
- implement support for pyrenees (N9) and himalaya (N950) OMAP DSS displays
- add DT OMAP DSS parts necessary to omap-n9.dts and omap-n950.dts
In 3.5.3 that stuff was in the following files (list may not be complete):
- https://github.com/filippz/kernel-ad...el-nokia-dsi.c (taal, himalaya and pyrenees)
- https://github.com/filippz/kernel-ad...lays/ctrl-gf.c (mentions himalaya specific hacks)
- https://github.com/filippz/kernel-ad.../board-rm680.c
Good news: display driver might be ready in https://github.com/torvalds/linux/bl...panel-dsi-cm.c (taal is mentioned there, probably needs tweaking for himalaya and pyrenees). Seems that there were plans for adding other display types into it, but were abandoned: https://github.com/torvalds/linux/co...096b825326d3e2 Bad news: I really don't know enough about this to be able to port these parts myself Any volunteers
Last edited by filip.pz; 2015-10-09 at 09:54. Reason: fixed display code names
|
|
2015-09-26
, 09:34
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#44
|
For people using Ubuntu 14.04 or its derivatives: you need gcc < 4.8 or >= 4.8.3.
I'm building the 4.9 compiler from Wily and see what happens next.
/edit: I'm lazy and I'll be using the toolchain from the ppa. https://launchpad.net/~terry.guo/+ar...c-arm-embedded
Last edited by marmistrz; 2015-09-26 at 15:10.
I'm building the 4.9 compiler from Wily and see what happens next.
/edit: I'm lazy and I'll be using the toolchain from the ppa. https://launchpad.net/~terry.guo/+ar...c-arm-embedded
__________________
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-09-26 at 15:10.
| The Following 2 Users Say Thank You to marmistrz For This Useful Post: | ||
|
|
2015-09-26
, 12:44
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#45
|
Will this script make sense for N950? (I care only about booting right now) Or should I add/remove something: https://github.com/marmistrz/debian9...debian_n950.sh
Yes, the repo is messy, but I'll try to do something for multi-device when we have it working on n950/n9.
Yes, the repo is messy, but I'll try to do something for multi-device when we have it working on n950/n9.
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
|
2015-09-26
, 18:43
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#46
|
Originally Posted by filip.pz
OK, I'm even more confused than before (I didn't think if that was even possible)
In 3.5.3 that stuff was in the following files
- https://github.com/filippz/kernel-ad...lays/ctrl-gf.c(mentions himalaya specific hacks)
I was trying to write dts part by looking at the board file, schematics and other similar boards. According to schematics (known to be faulty) and board file from 3.5 I've noticed that display is powered from vmmc2 and from vio (both from twl5031). So I connected vdd-supply of dsi to vmmc2 (https://www.kernel.org/doc/Documenta...,omap3-dss.txt) but there is nowhere to connect vio. By looking in 3.5 I noticed that the user of that supply is ctrl-gf.c, which is driver for TC358710XBG (MIPIŽ DISPLAY HUB/BRIDGE). Cool, another thing to port I'm thinking
But... strangest thing: that driver is not being used in 3.5 (#CONFIG_CTRL_GF is not set), but is being used in 2.6 (CONFIG_CTRL_GF=y)
My best guess: at some point one of development versions of our devices was in need of multiple DSI outputs (OMAP3 has only one) and that chip was chosen to provide them (for multiple displays or what
) Seems that driver and CONFIG_CTRL_GF=y where left together with supply entries in board file by mistake.If anyone has another explanation I'd like to hear it, but for now I'm assuming that second power supply (vio) is to be ignored.
|
|
2015-09-26
, 19:44
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#47
|
Filip,
I have absolutely no idea about this. Maybe pali will know something.
I have absolutely no idea about this. Maybe pali will know something.
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
|
|
2015-09-29
, 21:13
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#48
|
ok, I tried the script as uploaded in #45, something weird happens:
I'll setup ubiboot later on.
Code:
The following packages will be REMOVED: systemd-sysv The following NEW packages will be installed: firmware-ti-connectivity sysvinit-core 0 upgraded, 2 newly installed, 1 to remove and 1 not upgraded. Need to get 986 kB of archives. After this operation, 3938 kB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian/ jessie/main sysvinit-core armhf 2.88dsf-59 [129 kB] Get:2 http://httpredir.debian.org/debian/ jessie/non-free firmware-ti-connectivity all 0.43 [857 kB] Fetched 986 kB in 3s (315 kB/s) Preconfiguring packages ... dpkg: systemd-sysv: dependency problems, but removing anyway as you requested: init depends on systemd-sysv | sysvinit-core | upstart; however: Package systemd-sysv is to be removed. Package sysvinit-core is not installed. Package upstart is not installed. (Reading database ... 16312 files and directories currently installed.) Removing systemd-sysv (215-17+deb8u2) ... Processing triggers for man-db (2.7.0.2-5) ... Selecting previously unselected package sysvinit-core. (Reading database ... 16295 files and directories currently installed.) Preparing to unpack .../sysvinit-core_2.88dsf-59_armhf.deb ... Unpacking sysvinit-core (2.88dsf-59) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up sysvinit-core (2.88dsf-59) ... Not restarting sysvinit Selecting previously unselected package firmware-ti-connectivity. (Reading database ... 16320 files and directories currently installed.) Preparing to unpack .../firmware-ti-connectivity_0.43_all.deb ... Unpacking firmware-ti-connectivity (0.43) ... Setting up firmware-ti-connectivity (0.43) ... Stage 1 of installation complete. Copy configure_u-boot.sh to the N900 and execute it to complete installation. Installation failed
| The Following User Says Thank You to marmistrz For This Useful Post: | ||
 |
|
2015-09-29
, 22:31
|
|
Posts: 634 |
Thanked: 3,266 times |
Joined on May 2010
@ Colombia
|
#49
|
Originally Posted by marmistrz
In DebiaN900, the installation of System V init and removal of systemd is intentional. You can clear the $INIT variable in debian.conf if you want to keep systemd.
ok, I tried the script as uploaded in #45, something weird happens:
I'll setup ubiboot later on.Code:The following packages will be REMOVED: systemd-sysv The following NEW packages will be installed: firmware-ti-connectivity sysvinit-core 0 upgraded, 2 newly installed, 1 to remove and 1 not upgraded. Need to get 986 kB of archives. After this operation, 3938 kB of additional disk space will be used. Get:1 http://httpredir.debian.org/debian/ jessie/main sysvinit-core armhf 2.88dsf-59 [129 kB] Get:2 http://httpredir.debian.org/debian/ jessie/non-free firmware-ti-connectivity all 0.43 [857 kB] Fetched 986 kB in 3s (315 kB/s) Preconfiguring packages ... dpkg: systemd-sysv: dependency problems, but removing anyway as you requested: init depends on systemd-sysv | sysvinit-core | upstart; however: Package systemd-sysv is to be removed. Package sysvinit-core is not installed. Package upstart is not installed. (Reading database ... 16312 files and directories currently installed.) Removing systemd-sysv (215-17+deb8u2) ... Processing triggers for man-db (2.7.0.2-5) ... Selecting previously unselected package sysvinit-core. (Reading database ... 16295 files and directories currently installed.) Preparing to unpack .../sysvinit-core_2.88dsf-59_armhf.deb ... Unpacking sysvinit-core (2.88dsf-59) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up sysvinit-core (2.88dsf-59) ... Not restarting sysvinit Selecting previously unselected package firmware-ti-connectivity. (Reading database ... 16320 files and directories currently installed.) Preparing to unpack .../firmware-ti-connectivity_0.43_all.deb ... Unpacking firmware-ti-connectivity (0.43) ... Setting up firmware-ti-connectivity (0.43) ... Stage 1 of installation complete. Copy configure_u-boot.sh to the N900 and execute it to complete installation. Installation failed
The reason is says "Installation failed" is because you removed this line so the script automatically calls the clean_up() function when it exits.
If you want to learn more about the trap shell built-in utility and how it works, you can find the POSIX definition here.
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.
Mobile devices with mainline Linux support - Help needed with documentation.
"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
|
|
2015-10-04
, 11:13
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#50
|
I've tried setting up ubiboot, I get something like (I'll have access to the device tomorrow and may paste the exact message then)
"Booting the kernel failed. Please run maintenance boot"
Is there any way to find out what has failed, without setting up an external serial console? No such file or directory? Unable to mount?
"Booting the kernel failed. Please run maintenance boot"
Is there any way to find out what has failed, without setting up an external serial console? No such file or directory? Unable to mount?
I can compile mer-n9-2.6.32-latest-nokia-pr1.3 with Open Mode patch.
- but do I have correct xxx_defconfig is unknown
Is there something secret thing to be done, because I try new kernel with ubiboot (easier would be just flash new version)
- my version shut down without any evidence what went wrong
Janne