Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 6 hrs ago - more...
 |
|
2015-12-07
, 18:55
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#102
|
Another progress update - no big ones this time, just to keep the thing going 
I've completed twl5031 BCC driver and USB now detects if something is plugged in and device type (from charging point of view). This allows for usb-moded from Mer to start up, which in turn allows USB networking to be started so we can SSH into Nemo.
I've also completed Vibra support for N9. N950 uses different Vibration system - tied with twl5031/4030 audio system, so this will be done at that stage.
LED support is ready on N9 (lp5521 chip). Since N950 uses a bit different chip (lp5523), someone with N950 will have to do the work (shouldn't be too hard - probably just needs entries in DTS file). Small patch was required to MCE (already accepted), and lp5521 driver form mainline was also patched.
I also made an error of not including CONFIG_CPUFREQ_DT in kernel config which made N9 run @600 MHz (AFAIK), but even with it, system would run @800MHz only and some additional entries in DTS are needed to enable full 1GHz speed. With this change and by stopping pulseaudio service (restarts all the time due to no audio support at this time, consuming much of CPU time) N9 seems to be more responsive. Sadly I still get
every time lipstick (or fingerterm, for example) uses GPU. If anybody has any idea how to prevent this now it would be a good time to speak out.
I'm currently going mad with apds990x driver (ALS/PS sensor) and I hope it well be ready soon. Unfortunately N950 doesn't use that chip, so no support for it at this time. In userspace some Mer packages need patching for it to work: boardname (patch pending acceptance) and sensorfw (patch not ready at this time)
Progress report will be available from time to time - as usual.
Last edited by filip.pz; 2015-12-07 at 21:36.
I've completed twl5031 BCC driver and USB now detects if something is plugged in and device type (from charging point of view). This allows for usb-moded from Mer to start up, which in turn allows USB networking to be started so we can SSH into Nemo.
I've also completed Vibra support for N9. N950 uses different Vibration system - tied with twl5031/4030 audio system, so this will be done at that stage.
LED support is ready on N9 (lp5521 chip). Since N950 uses a bit different chip (lp5523), someone with N950 will have to do the work (shouldn't be too hard - probably just needs entries in DTS file). Small patch was required to MCE (already accepted), and lp5521 driver form mainline was also patched.
I also made an error of not including CONFIG_CPUFREQ_DT in kernel config which made N9 run @600 MHz (AFAIK), but even with it, system would run @800MHz only and some additional entries in DTS are needed to enable full 1GHz speed. With this change and by stopping pulseaudio service (restarts all the time due to no audio support at this time, consuming much of CPU time) N9 seems to be more responsive. Sadly I still get
Code:
pvr: lipstick: IOCTL 70 failed (13)
I'm currently going mad with apds990x driver (ALS/PS sensor) and I hope it well be ready soon. Unfortunately N950 doesn't use that chip, so no support for it at this time. In userspace some Mer packages need patching for it to work: boardname (patch pending acceptance) and sensorfw (patch not ready at this time)
Progress report will be available from time to time - as usual.
Last edited by filip.pz; 2015-12-07 at 21:36.
|
|
2015-12-07
, 19:21
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#103
|
And now some problems report 
I have the following ubiboot.conf: http://paste.ubuntu.com/13796513/
I added three entries, but only the 4.3-rc2 is displayed. Any ideas why?
I have the following ubiboot.conf: http://paste.ubuntu.com/13796513/
I added three entries, but only the 4.3-rc2 is displayed. Any ideas why?
|
|
2015-12-07
, 19:23
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#104
|
Originally Posted by marmistrz
G_OS5_NUM should be 2
And now some problems report
I have the following ubiboot.conf: http://paste.ubuntu.com/13796513/
I added three entries, but only the 4.3-rc2 is displayed. Any ideas why?
|
|
2015-12-07
, 19:27
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#105
|
Thanks.
With 3.5.3 Debian refuses to boot (black screen). How to debug it?
To post #100. Well, I guess you should simply stop rebasing
Is there anything that you could give to danpio? Is there anything danpio wants?
With 3.5.3 Debian refuses to boot (black screen). How to debug it?
To post #100. Well, I guess you should simply stop rebasing
Is there anything that you could give to danpio? Is there anything danpio wants?
|
|
2015-12-07
, 19:37
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#106
|
Originally Posted by marmistrz
I guess without working serial cable you are forced to be really creative (for example write some file at different "init point" and check for its existence after reboot)
With 3.5.3 Debian refuses to boot (black screen). How to debug it?
Maybe minimos could spare some time and try to debug it for you?
Originally Posted by marmistrz
Well, no one expressed desire to look at CMT or BME. I guess anything on that list is free for taking (apart form apds990x, and things reported working earlier)
To post #100. Well, I guess you should simply stop rebasing
Is there anything that you could give to danpio? Is there anything danpio wants?
Last edited by filip.pz; 2015-12-07 at 19:43.
|
|
2015-12-07
, 21:31
|
|
Posts: 165 |
Thanked: 625 times |
Joined on Oct 2012
|
#107
|
Originally Posted by marmistrz
First, you can check ubiboot log file to see if it goes successfully until executing the kernel used by Debian. If ubiboot is happy, you should check Debian syslog logs to see if there are any logs about this boot attempt. If not, it usually means that either the kernel didn't boot successfully, or userspace has crashed very early, and this makes debugging much harder. If logs exist, you should check them to see what went wrong.
Thanks.
With 3.5.3 Debian refuses to boot (black screen). How to debug it?
BTW, remember that in Debian, you should have started kicking watchdog files from early in the boot process (usually, both in its initrd/initramfs, and after continuing the boot process by some simple service.
__________________
My N9 apps: MeeTeleGram, Dukto, Prayers, Saaghar, N9 Easy Boot
Donations are appreciated
My N9 apps: MeeTeleGram, Dukto, Prayers, Saaghar, N9 Easy Boot
Donations are appreciated
|
|
2015-12-12
, 19:20
|
|
Posts: 108 |
Thanked: 579 times |
Joined on Feb 2013
@ Požega, Croatia
|
#108
|
All sensors are now functional on N9:
Sadly only lis302 is the same on both N9 and N950 (positioned a bit differently). N950 uses bh1770glc/sfh7770 for ALS/PS (supported in kernel), but magnetometer ak8974 is tricky one (no support for it mainline).
In Mer/Nemo, ALS/PS and accelerometer work by adding appropriate config file to sensorfw package, but ak8975 needs additional coding (since driver in mainline is quite different than the old one). I have that code ready, but I'm unsure how to properly test it so I'll try to get some info about that during next week.
I'll move onto audio bits after sensorfw is done (since we have 3 audio chips this could be rather complicated).There are still important things left to be done (apart from missing bits for N950) like CMT and BME, so I hope someone might take a shot at those.
On the following link are current kernel patches: https://www.dropbox.com/s/ogx2nbzoxf...x.tar.bz2?dl=1 Consider them to be tentative (not final in any way, shape, form or fashion) and that file will simply be overwritten with fresh patches from time to time.
- apds990x (ALS/PS = combined ambient light / proximity)
- lis302 (accelerometer)
- ak8975 (magnetometer)
Sadly only lis302 is the same on both N9 and N950 (positioned a bit differently). N950 uses bh1770glc/sfh7770 for ALS/PS (supported in kernel), but magnetometer ak8974 is tricky one (no support for it mainline).
In Mer/Nemo, ALS/PS and accelerometer work by adding appropriate config file to sensorfw package, but ak8975 needs additional coding (since driver in mainline is quite different than the old one). I have that code ready, but I'm unsure how to properly test it so I'll try to get some info about that during next week.
I'll move onto audio bits after sensorfw is done (since we have 3 audio chips this could be rather complicated).There are still important things left to be done (apart from missing bits for N950) like CMT and BME, so I hope someone might take a shot at those.
On the following link are current kernel patches: https://www.dropbox.com/s/ogx2nbzoxf...x.tar.bz2?dl=1 Consider them to be tentative (not final in any way, shape, form or fashion) and that file will simply be overwritten with fresh patches from time to time.
|
|
2015-12-12
, 21:38
|
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#109
|
Originally Posted by hedayat
Does the syslog remain after the unsuccessful boot?
First, you can check ubiboot log file to see if it goes successfully until executing the kernel used by Debian. If ubiboot is happy, you should check Debian syslog logs to see if there are any logs about this boot attempt. If not, it usually means that either the kernel didn't boot successfully, or userspace has crashed very early, and this makes debugging much harder. If logs exist, you should check them to see what went wrong.
BTW, remember that in Debian, you should have started kicking watchdog files from early in the boot process (usually, both in its initrd/initramfs, and after continuing the boot process by some simple service.
How can I start kicking the watchdog? Can I disable it as we did with our N900s?
|
|
2015-12-15
, 08:49
|
|
Posts: 165 |
Thanked: 625 times |
Joined on Oct 2012
|
#110
|
Does the syslog remain after the unsuccessful boot?
How can I start kicking the watchdog? Can I disable it as we did with our N900s?
Kicking watchdog can be achieved using a simple infinite while loop with an echo command to a special device file. I don't remember the device file now but others can help if you don't know it already. It is done in ubiboot too, or you can find it in Harmatten/Nemo/SFOS/Nitroid init scripts for N9.
__________________
My N9 apps: MeeTeleGram, Dukto, Prayers, Saaghar, N9 Easy Boot
Donations are appreciated
My N9 apps: MeeTeleGram, Dukto, Prayers, Saaghar, N9 Easy Boot
Donations are appreciated
Allthough. With this good progress i will probably regret LOL. (Just kidding. Ping me and its on its way)
You can still support my work by donation - click here