maemo.org - Talk - View Single Post

	daperl	2009-01-27 , 17:46
	Posts: 2,427 \| Thanked: 2,986 times \| Joined on Dec 2007	#66

Originally Posted by solca

It doesn't work with that patch. Exactly same as before.

My experiment failed. I added that patch and other ATAG and kexec patches (some by hand) from this site to the diablo 4.1.2 kernel. I then patched kexec-tools for armv6l. All was a no-go, but it wasn't like I really knew what I was doing. From a fanoush-like bootmenu, here was the script that caused my n800 to go blank and eventually shut off:

Code:

#! /bin/sh

/usr/local/sbin/kexec -l /boot/zImage "--append=root=1f03 rootfstype=jffs2 ro console=t
chvt 1 || true
killall5 -15
sleep 2
killall5 -9
umount -r /mnt/initfs
umount -r /
/usr/local/sbin/kexec -e

The middle part of this script is from /etc/init.d/minishutdown. Comments about what this script should be trying to do would be appreciated. But because of the active kexec development since 2.6.21, I'm less-than-skeptical that patching a 2.6.21 kernel is the right way to go. And this is also the reason, unless anyone can suggest something obvious, that I'm unlikely to try and further debug this simple experiment.

Here's what processes were running at the time:

Code:

  PID  Uid        VSZ Stat Command
    1 root       1888 RW  /bin/sh /sbin/init 2
    2 root            SWN [ksoftirqd/0]
    3 root            SW  [watchdog/0]
    4 root            SW< [events/0]
    5 root            SW< [khelper]
    6 root            SW< [kthread]
   14 root            SW< [dvfs/0]
   66 root            SW< [kblockd/0]
   67 root            SW< [kseriod]
   79 root            SW< [OMAP McSPI/0]
   86 root            SW< [ksuspend_usbd]
   89 root            SW< [khubd]
  113 root            SW  [pdflush]
  114 root            SW  [pdflush]
  115 root            SW< [kswapd0]
  116 root            SW< [aio/0]
  119 root            SW< [mipid_esd]
  238 root            SW  [mtdblockd]
  280 root            SW< [kondemand/0]
  281 root            SW< [kmmcd]
  292 root            SW< [krfcommd]
  307 root            SW< [mmcqd]
  343 root            SW< [mmcqd]
  350 root       1072 SW< dsme -d -l syslog -v 4 -p /usr/lib/dsme/libstartup.so
  358 root        804 SW  /usr/bin/bme_RX-34
  360 root        564 SW  /usr/sbin/kicker
  494 root            SW< [cx3110x]
  539 root       1960 RW  ps

And here is my current opinion:

If Nokia is serious about minimal mid-term support of n8x0 hardware, they need to release the NoLo secondary code. Much time, energy and resources could be saved. I would go as far as saying that some people would sign ND agreements if necessary. We need a flexible, grub-like, blob.

Most people like smooth transitions, so unless they can easily bounce back to their working Maemo 4.1.2, they're less likely to experiment with a 2.6.27 Mer bleeding edge. I'm not sure I could be convinced otherwise, but I don't think on-tablet kernel/initfs flashing is a solution. It's cool... but not a solution. Just look at the ease of trying-out the other OS/WM projects that shared a kernel. Now it's time for multiple kernels and their modules to share some hardware.

In the meantime, I'll see if there's anything I can do for the Mer project and I'll be patiently waiting for n8x0-compatible Fremantle binaries.

__________________
N9: Go white or go home

Quote & Reply |