maemo.org - Talk
Page 3 of 4 12 3 4
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)
-   -   The N9/N950 Kernel Upstreaming Force (https://talk.maemo.org/showthread.php?t=95966)

peterleinchen 2015-11-13 21:29
Re: The N9/N950 Kernel Upstreaming Force
 
filip.pz

I only get
Quote:
# ./mxt-app
sh: mxt-app: not found
downloaded, copied to /root, made executable, used your command ...

meemorph 2015-11-13 21:37
Re: The N9/N950 Kernel Upstreaming Force
 
same here
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.xcfg
sh: ./mxt-app: not found

ls -al
-rwxr-xr-x    1 root    root        290144 Nov 13 22:31 mxt-app

uname -a
Linux RM680 2.6.32.54-dfl61-20121301 #1 PREEMPT Sat Mar 2 23:11:21 EET 2013 armv7l GNU/Linux

filip.pz 2015-11-14 05:42
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by meemorph (Post 1488121)
same here
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.xcfg
sh: ./mxt-app: not found

ls -al
-rwxr-xr-x    1 root    root        290144 Nov 13 22:31 mxt-app

uname -a
Linux RM680 2.6.32.54-dfl61-20121301 #1 PREEMPT Sat Mar 2 23:11:21 EET 2013 armv7l GNU/Linux
Sorry guys. I have built it with Mer SDK and tried it on Nemo. Seems that Harmattan has unmet dependencies. I'll check what's missing during the day and report back.

minimos 2015-11-14 08:50
Re: The N9/N950 Kernel Upstreaming Force
 
I tried to run under strace but it did not seem to help much:

Code:
/tmp # strace -F ./mxt-app
execve("./mxt-app", ["./mxt-app"], [/* 35 vars */]) = -1 ENOENT (No such file or directory)
dup(2)                                  = 3
fcntl64(3, F_GETFL)                    = 0x20002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3aaab000
_llseek(3, 0, 0xaebef668, SEEK_CUR)    = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3)                                = 0
munmap(0x3aaab000, 4096)                = 0
exit_group(1)                          = ?

filip.pz 2015-11-14 09:07
Re: The N9/N950 Kernel Upstreaming Force
 
Fixed by recompilation of mxt-app without libusb1 support (download from the same link: https://www.dropbox.com/s/tutr6hueizgn7w9/mxt-app?dl=0). Also, this is needed:
Code:
ln -s /lib/ld-linux.so.3 /lib/ld-linux-armhf.so.3
This will get you to interactive mode, if someone wants to play:
Code:
./mxt-app -d i2c-dev:2-004b

peterleinchen 2015-11-14 09:31
Re: The N9/N950 Kernel Upstreaming Force
 
Sadly, same thing happening.

--
Oops, sorry. Forgot the link. Stay tuned ...

Okay it is running. But with error message.
Quote:
~ # ./mxt-app -d i2c-dev:2-004b
Version:1.26-5-g5a0e692-mod
Registered i2c-dev adapter:2 address:0x4b
Error Operation not permitted (1) writing to i2c
Failed to read ID information
~ #
and no output written.

I am on stock kernel (PR1.3,
Quote:
~ # uname -r
2.6.32.54-dfl61-20121301
). As root , and in develsh.
So I guess open mode is needed?

meemorph 2015-11-14 10:47
Re: The N9/N950 Kernel Upstreaming Force
 
with open mode kernel as in comment above:
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.xcfg
Version:1.26-5-g5a0e692-mod
Registered i2c-dev adapter:2 address:0x4b
REPORTALL command issued
Read config from device
Saved config to RM-680_Himalaya_AUO_V1_1.xcfg in .xcfg format
http://pastebin.com/mx4t5SsC

filip.pz 2015-11-16 16:34
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by meemorph (Post 1488139)
with open mode kernel as in comment above:
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.xcfg
Version:1.26-5-g5a0e692-mod
Registered i2c-dev adapter:2 address:0x4b
REPORTALL command issued
Read config from device
Saved config to RM-680_Himalaya_AUO_V1_1.xcfg in .xcfg format
http://pastebin.com/mx4t5SsC
Sorry to bother you again, but can you do:
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.raw
Apparently driver needs OBP_RAW format and conversion from xcfg to raw doesn't produce valid OBP_RAW file.

meemorph 2015-11-16 18:47
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by filip.pz (Post 1488298)
Sorry to bother you again, but can you do:
Code:
./mxt-app -d i2c-dev:2-004b --save RM-680_Himalaya_AUO_V1_1.raw
...
null problemo, nema problema, no problem :D

Code:
Version:1.26-5-g5a0e692-mod
Registered i2c-dev adapter:2 address:0x4b
REPORTALL command issued
Read config from device
Saved config to RM-680_Himalaya_AUO_V1_1.raw in OBP_RAW format
http://pastebin.com/0nqFVUYy

https://www.dropbox.com/s/jpwayi9gb9..._V1_1.raw?dl=0

marmistrz 2015-11-16 21:45
Re: The N9/N950 Kernel Upstreaming Force
 
Hi,

I'm still there, just really busy

Here's the dump for the N950.
http://en.file-upload.net/download-1...M-696.raw.html

Thanks

meemorph 2015-11-17 18:11
Quote:
Originally Posted by marmistrz (Post 1488316)
...
Here's the dump for the N950.
http://en.file-upload.net/download-1...M-696.raw.html
...
Is RM-696* a good filename for RAW data of a N950? RM-680* sounds better to not comfuse with N9. ;-)

filip.pz 2015-11-17 18:39
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by meemorph (Post 1488398)
Is RM-696* a good filename for RAW data of a N950? RM-680* sounds better to not comfuse with N9. ;-)
It's all good - I had to do some manual patching anyway. Files are placed in nemo-configs-n950-n9 (https://git.merproject.org/filippz/n...0fbb0180e70572) and names/data should be OK. I've tested on N9 and I do get some messages from the driver when pressing around screen trough mxt-app. Still, I don't get anything from /dev/input/eventN, maybe because lipstick/qt is processing those messages and they don't get to that point. Unfortunately lipstick is just sitting there not reacting to pressing power button or touching the screen - but that seems unrelated.

marmistrz 2015-11-18 16:16
Re: The N9/N950 Kernel Upstreaming Force
 
Yep, my mistake, mixed up the codenames.

Well, I'd suggest using Debian. See marmistrz/debian900 on GitHub.

I only regret to say I don't know whether this setup works at all on N9/N950. I've been really busy since a month or so and I won't probably have more free time for another month or so

But if you need some quick test/dump from N950, let me know, I'll see what I can do.

News: danpio offered his help.

danpio 2015-11-18 21:40
Re: The N9/N950 Kernel Upstreaming Force
 
Hi
Yes I confirm my help :)

but i need get some task to job :D

filip.pz 2015-11-21 15:43
Re: The N9/N950 Kernel Upstreaming Force
 
Progress update: touschreen and wlan now work on 4.4.0-rc1:
https://www.dropbox.com/s/zajzpglsht..._WLAN.JPG?dl=1

Everything is quite laggy probably because of some 99% of time when something gets rendered on screen I get
Code:
pvr: lipstick: IOCTL 70 failed (13)
It may well be that PVR is not to blame here, because Nemo boot time is about 25% slower than with 3.5.3, and it may just be that IOCTL 70 (PVRSRV_BRIDGE_EVENT_OBJECT_WAIT) times out (13 = PVRSRV_ERROR_TIMEOUT) because of CPU being occupied with something else all the time.

marmistrz 2015-11-21 17:33
Re: The N9/N950 Kernel Upstreaming Force
 
I had a while today and tried to boot Debian on the old 3.5.3 kernel. I disabled autoboot in Ubiboot, but it still tries to autoboot the non-existent kernel.

Does Ubiboot need me to enter Harmattan for the changes in config to populate?

filip.pz 2015-11-21 17:37
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1489082)
Does Ubiboot need me to enter Harmattan for the changes in config to populate?
After making changes to ubiboot.conf I always had to reboot first because ubiboot always used old settings (tbh I use easyboot these days - mabye "plain" ubiboot works OK)

juiceme 2015-11-21 21:21
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1489082)
I had a while today and tried to boot Debian on the old 3.5.3 kernel. I disabled autoboot in Ubiboot, but it still tries to autoboot the non-existent kernel.

Does Ubiboot need me to enter Harmattan for the changes in config to populate?
No, there's nothing tied to Harmattan in ubiboot, it is just one of the possible OS'es that yo can use.

marmistrz 2015-11-25 21:36
Re: The N9/N950 Kernel Upstreaming Force
 
filip.pz: feel free to assign any tasks to anyone. I'm very busy these days, so I might not be able to coordinate everything. Besides, you know what's needed most this very moment.

In particular danpio asked for some task. Can you please give him something?

filip.pz 2015-11-26 06:30
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1489778)
filip.pz: feel free to assign any tasks to anyone. I'm very busy these days, so I might not be able to coordinate everything. Besides, you know what's needed most this very moment.

In particular danpio asked for some task. Can you please give him something?
Well there is still a matter of adding a table on elinux.org :)

As for "real kernel development", I'm currently working on twl5031_bbc driver (replacement for twl4030_bci) which is needed in order for usb-moded from Mer to even start - bringing us closer to possibility of getting ssh over usb to work (at least on Mer/Nemo)

There's a lot of thing left to do (IIRC):
  • sensors for proximity, ambiental light, magnetometer, accelerometer
  • Audio parts
  • CMT (modem, migth be same or at least very similar to the one on N900, so we should reuse Palis work)
  • Bluetooth
  • BME support (battery charging) - we should check if BME used on N900 matches the one on N9/950, since the one from N900 has been reverse engineered. If it's not 100% compatible we should then fix that, which is still a better option than patching twl4030_madc in kernel so that old BME binary blob can talk to it
  • Vibration/haptics
  • NFC support
  • GPS support (simple driver exists, but userspace must speak proprietary MEIF)
  • ECI/ACI - whatever is called (support for controls on wired earphones - undocumented in twl5031 IIRC)
  • TV out (depends on ECI/ACI for detection of cable connection)
  • FM radio
  • ...
Also N950 specific stuff:
  • LCD panel support
  • touchscreen (completed/untested)
  • keyboard (completed/untested)
  • support for keyboard slide event (completed/untested)
  • LED support (N9 uses LP5521, N950 uses LP5523)
  • WLAN support (same wl1271 module as on N9, but connected in a different way)

If someone would be interested in CMT (my N9 has broken CMT chip and is not fully functional in that regard) and/or BME (mostly done in userspace, N900 guys can help us with that) that would be awesome.

Since I'm rebasing and rewriting history in git all the time (not good for collaboration) I'm not sure what would be the best way for others to contribute, so I'm open to suggestions in that regard.

nieldk 2015-11-26 17:29
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by filip.pz (Post 1489818)
Well there is still a matter of adding a table on elinux.org :)

As for "real kernel development", I'm currently working on twl5031_bbc driver (replacement for twl4030_bci) which is needed in order for usb-moded from Mer to even start - bringing us closer to possibility of getting ssh over usb to work (at least on Mer/Nemo)

There's a lot of thing left to do (IIRC):
  • sensors for proximity, ambiental light, magnetometer, accelerometer
  • Audio parts
  • CMT (modem, migth be same or at least very similar to the one on N900, so we should reuse Palis work)
  • Bluetooth
  • BME support (battery charging) - we should check if BME used on N900 matches the on on N9/950, since the one from N900 has been reverse engineered. If it's not 100% compatible we should then fix that, which is still a better option than patching twl4030_madc in kernel so that old BME binary blob can talk to it
  • NFC support
  • GPS support (simple driver exists, but userspace must speak proprietary MEIF)
  • ECI/ACI - whatever is called (support for controls on wired earphones - undocumented in twl5031 IIRC)
  • TV out (depends on ECI/ACI for detection of cable connection)
  • FM radio
  • ...
Also N950 specific stuff:
  • LCD panel support
  • touchscreen (completed/untested)
  • keyboard (completed/untested)
  • support for keyboard slide event (completed/untested)
  • LED support (N9 uses LP5521, N950 uses LP5523)
  • WLAN support (same wl1271 module as on N9, but connected in a different way)

If someone would be interested in CMT (my N9 has broken CMT chip and is not fully functional in that regard) and/or BME (mostly done in userspace, N900 guys can help us with that) that would be awesome.

Since I'm rebasing and rewriting history in git all the time (not good for collaboration) I'm not sure what would be the best way for others to contribute, so I'm open to suggestions in that regard.
Friendly reminder that a fully functional. Black. 64G (scandinavia) N9 is waiting a proper home.
Allthough. With this good progress i will probably regret LOL. (Just kidding. Ping me and its on its way)

filip.pz 2015-12-07 18:55
Re: The N9/N950 Kernel Upstreaming Force
 
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
Code:
pvr: lipstick: IOCTL 70 failed (13)
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.

marmistrz 2015-12-07 19:21
Re: The N9/N950 Kernel Upstreaming Force
 
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?

filip.pz 2015-12-07 19:23
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1490817)
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?
G_OS5_NUM should be 2 ;)

marmistrz 2015-12-07 19:27
Re: The N9/N950 Kernel Upstreaming Force
 
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 :D
Is there anything that you could give to danpio? Is there anything danpio wants?

filip.pz 2015-12-07 19:37
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1490819)
With 3.5.3 Debian refuses to boot (black screen). How to debug it?
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)
Maybe minimos could spare some time and try to debug it for you?

Quote:
Originally Posted by marmistrz (Post 1490819)
To post #100. Well, I guess you should simply stop rebasing :D
Is there anything that you could give to danpio? Is there anything danpio wants?
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)

hedayat 2015-12-07 21:31
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1490819)
Thanks.

With 3.5.3 Debian refuses to boot (black screen). How to debug it?
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.

filip.pz 2015-12-12 19:20
Re: The N9/N950 Kernel Upstreaming Force
 
All sensors are now functional on N9:
  • 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.

marmistrz 2015-12-12 21:38
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by hedayat (Post 1490830)
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.
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?

hedayat 2015-12-15 08:49
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Does the syslog remain after the unsuccessful boot?
I doubt that syslog gets the chance to even start. Kicking watchdog should start immediately when control reaches Debian (the first thing to be executed by its init script).

Quote:
How can I start kicking the watchdog? Can I disable it as we did with our N900s?
It depends on your init system. If using systemd, it should be the first service to be started. If using SysV init, you can put it on top of main init script to be started in the background.

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.

filip.pz 2015-12-15 16:16
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1491336)
How can I start kicking the watchdog? Can I disable it as we did with our N900s?
AFAIK you can disable watchdogs by flasher (disabling = not starting), but they still get activated later on because ubiboot starts kicking them. Once they start they can't be disabled until reboot and something has to kick them all the time (Mer uses DSME, and ubiboot has simple script to do so: https://talk.maemo.org/showpost.php?...8&postcount=20). It may be possible to disable them with flasher and to disable ubiboot from kicking them, but I never tried it myself.

filip.pz 2015-12-24 16:22
Re: The N9/N950 Kernel Upstreaming Force
 
Christmas progress update:

Audio parts now work (for the most part at least). N9/N950 use quite complex setup consisting of TWL4030, TLV320DAC33 and WL1273 codecs. TWL4030 is used as main audio chip, paired with TLV320DAC33 for handsfree and headphones output (for better sound quality I suppose). TPA6140A2 (headphones amplifier) is connected to TLV320DAC33, and in the end WL1273 is used for FM radio and bluetooth connectivity.

I've used following script (test-sound.sh) to test TWL4030/TLV320DAC33 in Nemomobile:
Code:
#!/bin/sh

echo "Test earpiece"
pactl set-sink-port sink.hw0 nokia-n950-twl4030-output-earpiece
/usr/bin/paplay -v --device=sink.hw0 /usr/share/sounds/alsa/Noise.wav

echo "Test speaker"
pactl set-sink-port sink.hw0 nokia-n950-twl4030-output-ihf
/usr/bin/paplay -v --device=sink.hw0 /usr/share/sounds/alsa/Noise.wav

echo "Test headphone"
/usr/bin/paplay -v --device=sink.headphone /usr/share/sounds/alsa/Noise.wav

echo "Test TWL4030 -> TLV320DAC33 passthrough"
#set TWL4030 to headset-call port which forwards output to TLV320DAC33
pactl set-sink-port sink.hw0 nokia-n950-twl4030-output-headset-call
#set TLV320DAC33 to passthrough profile to accept input from TWL4030
pactl set-card-profile dac33 passthrough
#play something to TWL4030 and see if it goes throught TLV320DAC33 to headphones
/usr/bin/paplay -v --device=sink.hw0 /usr/share/sounds/alsa/Noise.wav
pactl set-card-profile dac33 normal
We still need jack detection logic (if something is plugged into 3.5mm jack and what). After that I'm after ACI/ECI driver (support for input from wired earphones with music controls: play, pause, etc.)

Patches file (https://www.dropbox.com/s/ogx2nbzoxf...x.tar.bz2?dl=1) has been updated to latest patch set.

In the end, let me wish all of you a Merry Xmas and a Happy New Year

hedayat 2015-12-26 07:02
Re: The N9/N950 Kernel Upstreaming Force
 
Thanks a lot fillip.pz. I'm just really sorry that I can't still give you a hand yet. :(

filip.pz 2015-12-26 12:54
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by hedayat (Post 1492670)
Thanks a lot fillip.pz. I'm just really sorry that I can't still give you a hand yet. :(
No problem, but can you spare some time in the near future for CMT? My N9 doesn't work with SIM card (reboots after entering PIN) and you have some experience with ofono, so you are a prime candidate for this ;)

nieldk 2015-12-26 13:15
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by filip.pz (Post 1492685)
No problem, but can you spare some time in the near future for CMT? My N9 doesn't work with SIM card (reboots after entering PIN) and you have some experience with ofono, so you are a prime candidate for this ;)
This is still valid :)

http://talk.maemo.org/showpost.php?p...&postcount=101

hedayat 2015-12-28 06:47
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
No problem, but can you spare some time in the near future for CMT? My N9 doesn't work with SIM card (reboots after entering PIN) and you have some experience with ofono, so you are a prime candidate for this
I hope so. But my predictions has gone wrong recently many times! :P

marmistrz 2015-12-28 09:23
Re: The N9/N950 Kernel Upstreaming Force
 
Well, I must admit I really wish I had the time to devote for the project too. (finally get that Debian to work to have a clean base!!)

But my free time is like dragons. It theoretically should exist, but I've never seen it within the last 3 months ;(

wicket 2016-03-07 01:23
Re: The N9/N950 Kernel Upstreaming Force
 
I noticed that kernel hacker and Debian developer Sebastian Reichel (sre) who has done fantastic work mainlining N900 kernel patches has taken a recent interest in the N950:

http://elinux.org/N950

https://git.kernel.org/cgit/linux/ke...h=n950-display

https://git.kernel.org/cgit/linux/ke...og/?h=for-next

Pali's N900 kernel also includes N9/N950 specific patches that are yet to be mainlined.

filip.pz 2016-03-07 16:22
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by wicket (Post 1500803)
I noticed that kernel hacker and Debian developer Sebastian Reichel (sre) who has done fantastic work mainlining N900 kernel patches has taken a recent interest in the N950
I've taken the liberty and contacted Sebastian via e-mail.
Thanks for the heads up wicket!

danpio 2016-03-07 17:36
Re: The N9/N950 Kernel Upstreaming Force
 
Hi :)
I was looking a little on the net and I found the documentation to the SGX530 can help? :)

http://www.datasheetarchive.com/dl/D...AH00695714.pdf


All times are GMT. The time now is 10:50.
Page 3 of 4 12 3 4
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8