[Android] Eclair NITDroid (WIP) - Page 26 - maemo.org

mockillo | # 251 | 2010-03-07, 21:10 | Report

Has anyone ever seen this before?

Kernel sources from SDK, patched with android patches from bdogg64, disabled kernel debugging, enabled fbcon (unable to read anything from just before this happens as the screen backlight turns off after a few seconds) and added a local version.

Modules are all in the right place, as far as I know.

Touchscreen is WAY off, bottom right corner of the screen hits 7, the rest of the screen hits nothing as far as I can tell.

Keyboard isnt working either.

First theory is that the modules are not being loaded, but I'm not sure why not since they should be in the correct place.
I've also run depmod <kernel name> to generate all the correct modules.* files.

The console output I do however get to see does not give me any errors of missing modules/drivers when it starts to load, but it did this before I ran depmod <kernel name>, which is why I think the modules are in the correct place.

Any idea?

Oh, and please let me know if I should move this to a new thread, I just thought of posting it here since it has the android patches and might be related.

Has anyone started Maemo with a kernel with the android patches?

todor_tsankov | # 252 | 2010-03-07, 21:13 | Report

This screenshot seems like an Maemo initial screen just without the theme applied to it (I think this happens when you mess up the current theme)

mockillo | # 253 | 2010-03-07, 21:23 | Report

I havent touched anything besides the kernel and module.
If I flash Titan's zImage from Compiling custom kernels for P1.1 (with fiasco-gen) everything is back to normal.

mockillo | # 254 | 2010-03-07, 21:25 | Report

Besides, if it's just the theme, shouldn't the touchscreen/keyboard be working?

bdogg64 | # 255 | 2010-03-07, 23:13 | Report

Originally Posted by mockillo View Post

Besides, if it's just the theme, shouldn't the touchscreen/keyboard be working?

It should. The kernel I used to boot android is previous to the current PR 1.1.1 kernel, so I can't say how much difference there is in the 2 kernels. Were there any errors when you patched the kernel?

bdogg64 | # 256 | 2010-03-08, 00:10 | Report

I uploaded a new patched kernel based on the latest maemo sdk kernel source with the android patches. I'm assuming this is the same kernel on the PR 1.1.1 firmware

http://nitdroid.loadsofspace.net/zImage-20100307

md5: 2d9983ee38f675a12162b1dcb02f304e

I also attached an updated patch file. Here are the instructions of what I did. This assumes you have the up-to-date maemo 5 sdk installed, and are already logged in (e.g. /scratchbox/login)

Code:

mkdir android-kernel
cd android-kernel
fakeroot apt-get source kernel-source
tar zxf kernel_2.6.28.orig.tar.gz
cd kernel-2.6.28
patch -p1 <../kernel_2.6.28-20094803.3+0m5.diff
patch -p1 <../n900_kernel.patch
make ARCH=arm rx51_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- -j4 zImage modules

That should give you a zImage in the arch/arm/boot directory and the miscellaneous modules.

FYI: In order for the touchscreen to work, you need to backup the original tsc2005.ko module in the /lib/modules/current directory before replacing with the modules from the android kernel. After replacing the modules, place the original tsc2005.ko module back into the /lib/modules/current directory. The patched android touchscreen module conflicts with the maemo touchscreen module.

http://www.natisbad.org/N900/n900-custom-kernel.html has an updated tutorial on replacing the modules on the N900 also.

Attached Files

n900_kernel_patch-2010-03-07.tar.gz (277.3 KB, 103 views)

Last edited by bdogg64; 2010-03-08 at 22:30.

The Following 3 Users Say Thank You to bdogg64 For This Useful Post:
b-man, mrdally204, qole

dj_steve | # 257 | 2010-03-08, 10:36 | Report

@bdogg64

just found some code here you might find of interest it has to do with pageflipping in the omap fb driver

Code:

Index: linux-omap-2_6_23/drivers/video/omap/omapfb_main.c
===================================================================
--- linux-omap-2_6_23.orig/drivers/video/omap/omapfb_main.c
+++ linux-omap-2_6_23/drivers/video/omap/omapfb_main.c
@@ -168,7 +168,7 @@ static int ctrl_init(struct omapfb_devic
                /* 12 bpp is packed in 16 bits */
                if (bpp == 12)
                       bpp = 16;
-               def_size = def_vxres * def_vyres * bpp / 8;
+               def_size = def_vxres * def_vyres * 2 * bpp / 8;
                fbdev->mem_desc.region_cnt = 1;
                fbdev->mem_desc.region[0].size = PAGE_ALIGN(def_size);
        }
@@ -415,6 +415,7 @@ static void set_fb_fix(struct fb_info *f
        }
        fix->accel              = FB_ACCEL_OMAP1610;
        fix->line_length        = var->xres_virtual * bpp / 8;
+       fix->ypanstep           = 1;
 }

 static int set_color_mode(struct omapfb_plane_struct *plane,
@@ -1471,7 +1472,7 @@ static int fbinfo_init(struct omapfb_dev
        var->xres = def_vxres;
        var->yres = def_vyres;
        var->xres_virtual = def_vxres;
-       var->yres_virtual = def_vyres;
+       var->yres_virtual = def_vyres * 2;
        var->rotate       = def_rotate;
        var->bits_per_pixel = fbdev->panel->bpp;

its a patch i found at @ http://elinux.org/Android_on_OMAP#Pa...g_frame_buffer

mockillo | # 258 | 2010-03-08, 12:35 | Report

Originally Posted by bdogg64 View Post

I also attached an updated patch file. Here are the instructions of what I did. This assumes you have the up-to-date maemo 5 sdk installed, and are already logged in (e.g. /scratchbox/login)

Code:

mkdir android-kernel
cd android-kernel
fakeroot apt-get source kernel-source
tar zxf kernel_2.6.28.orig.tar.gz
cd kernel-2.6.28
patch -p1 <../kernel_2.6.28-20094803.3+0m5.diff
patch -p1 <../n900_kernel.patch
make ARCH=arm rx51_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- -j4 zImage modules

That should give you a zImage in the arch/arm/boot directory and the miscellaneous.

Thanks, I'll try this later tonight

mockillo | # 259 | 2010-03-08, 20:27 | Report

Did that exactly! Except that I crosscompiled with arm-linux-gnueabi- instead of arm-none-linux-gnueabi-. Moved the modules in place, ran depmod and tried to boot maemo. Got the same unthemed pincode screen with a terribly uncalibrated touchscreen.

Sigh!

mockillo | # 260 | 2010-03-08, 20:39 | Report

Funny thing, if I boot while in R&D mode, I get the theme but still no usable touchscreen. If I boot in production mode, I get no theme and no usable touchscreen.