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

bdogg64 | # 261 | 2010-03-08, 22:25 | Report

Originally Posted by mockillo View Post

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!

Of course I keep forgetting stuff ... For the touchscreen to work after you patch the kernel and modules, you need to keep the original tsc2005.ko module and place it back in the directory with the new modules. The patched touchscreen driver for android throws it off when you boot back into maemo.

I'm not sure whats going on with the keyboard, as mine wasn't affected after patching.

Hope this helps

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

bdogg64 | # 262 | 2010-03-08, 22:33 | Report

Originally Posted by dj_steve View Post

@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

I tried that before, but its for the old omapfb driver that the n8x0 uses. The N900 uses the new omap2 dss driver which doesn't have a similar patch yet, and I don't know enough about how it works to implement it on the new drivers/video/omap2/omapfb/omapfb- main.c driver.

dj_steve | # 263 | 2010-03-09, 20:08 | Report

right excuse the lack of updates last few days, busy with work

bdogg can you send me the omap drivers for n900 and ill see if i can look at them for you

twoboxen | # 264 | 2010-03-10, 03:59 | Report

I played with a friend's droid (not a euphemism) tonight. Man, that thing looks awesome. I'm not in love with the hardware, but the OS looks like a blast. Dual booting meego + android 2.x on the n900? All win.

This project is very exciting. I still couldn't get bootmenu to load the android kernel, but I'm trying again soon. Keep up the good work fellas! Much appreciated.

dj_steve | # 265 | 2010-03-10, 10:59 | Report

update time: been examining the contents of the original nitdroid patch for the android userspace and noticed one thing in one of the files thats a bit wrong in my opin :

file these are in is vendor/nokia/nit/BoardConfig.mk

Code:

TARGET_HARDWARE_3D      := false

HAVE_HTC_AUDIO_DRIVER   := false
HAVE_WEXT_WIFI_DRIVER   := true

BOARD_USES_GENERIC_AUDIO := true
BOARD_USES_ALSA_AUDIO   := false
BOARD_HAVE_BLUETOOTH    := true

both the bold lines seem to be slightly wrong for the NIT tablets,

i know for a fact the sound subsystem on the n8x0 runs via alsa so ive enabled that, also we all know the n900 and n800 both have internel 3d graphics hardware so thats enabled to.

am compiling a android 2.1r2 system now, wont get to test until i get home from work ~8pm tonight though

The Following 5 Users Say Thank You to dj_steve For This Useful Post:
Apoc, b-man, happyblob, mrdally204, twoboxen

mrdally204 | # 266 | 2010-03-10, 12:44 | Report

thanks for the updates guys. Steve i am interested to see what works after your changes.

bdogg64 | # 267 | 2010-03-10, 22:28 | Report

Originally Posted by dj_steve View Post

update time: been examining the contents of the original nitdroid patch for the android userspace and noticed one thing in one of the files thats a bit wrong in my opin :

file these are in is vendor/nokia/nit/BoardConfig.mk

Code:

TARGET_HARDWARE_3D      := false

HAVE_HTC_AUDIO_DRIVER   := false
HAVE_WEXT_WIFI_DRIVER   := true

BOARD_USES_GENERIC_AUDIO := true
BOARD_USES_ALSA_AUDIO   := false
BOARD_HAVE_BLUETOOTH    := true

both the bold lines seem to be slightly wrong for the NIT tablets,

i know for a fact the sound subsystem on the n8x0 runs via alsa so ive enabled that, also we all know the n900 and n800 both have internel 3d graphics hardware so thats enabled to.

am compiling a android 2.1r2 system now, wont get to test until i get home from work ~8pm tonight though

I wish it were that simple as turning on the flags. You still have to write interfaces and drivers that interact with the hardware. Here is a rough overview of the build process.

http://pdk.android.com/online-pdk/guide/index.html

The Following User Says Thank You to bdogg64 For This Useful Post:
linuxeventually

andoreasu | # 268 | 2010-03-11, 09:58 | Report

I don't know if this will help with the android kernel, but this guy seems to do a good job with the linux kernel on n8x0

http://franciscoalecrim.com/blog/category/n810/

see the first post to see how he got 2.6.33 working partially
see the second post to see how he got 2.6.29-omap working with full(?) hardware support on n810

I am new to maemo.org, and apologize if I posted something you already new all the time

The Following User Says Thank You to andoreasu For This Useful Post:
mrdally204

Cpasjuste | # 269 | 2010-03-12, 14:51 | Report

I'm sorry i did read a few pages but i can't read all the 27 pages ... so i have a question : are you guys trying to boot the nokia kernel patched with android patchs, but with the maemo rootfs ? If so, wouldn't it be easier to boot the patched android kernel with an android rootfs hosted on an microSD partition ?
Else i did successfully boot android on the pandora gaming console, and latest kernel use dss2 too. What i did is select the old omap-fb driver instead the dss one in the kernel configuration ( you have to disable the dss2 driver in kernel config before beeing able to see the omap-fb driver ) then patched it with the previous omapfb patchs posted here.

Well, i'm interessed in having android on the n900, could someone sumarize the current progress to see if i can help ?

Callensunny | # 270 | 2010-03-12, 17:56 | Report

I can't believe the WinMobile community is already ahead of us!! Mainly because WinMobile sucks so bad. See the link: http://pocketnow.com/tweaks-hacks/an...-pro2-it-rocks