[Android] NITDroid V2 Development Topic

[dj_steve]

hell yes, any chance you could integrate the pvr driver from milestone ? (can provide info if needed

[dj_steve]

Originally Posted by Jay-C

Just joined in, so _HELLO_ to everybody!

I've got a solution to the watchdog problem. With my patch it is possible to disable R&D mode, which is not possible at the moment because of a limitation in the wdt driver.

Actually, I have been integrating the Titan's kernel patches with the latest patches in android-common-2.6.29. Some highlights:

- Fully compatible dualboot: Maemo and Android
- WDT problem solved
- Touchscreen driver compatible with both Maemo and Android (module option to select)
- overclock capable
- nearly all Titan's modules included
- latest bug fixes from Nokia

... just to mention a few.

My plan is to make a initrd image, which includes the bootmenu, kernel modules, and templates to boot both Maemo and Android, without any changes to the existing Maemo system.

anybody interested in trying out my beta kernel?

cheers
jay

can you join the nitdroid irc room may be easier to discuss their

[Tiboric]

Originally Posted by Jay-C

Just joined in, so _HELLO_ to everybody!

I've got a solution to the watchdog problem. With my patch it is possible to disable R&D mode, which is not possible at the moment because of a limitation in the wdt driver.

Actually, I have been integrating the Titan's kernel patches with the latest patches in android-common-2.6.29. Some highlights:

- Fully compatible dualboot: Maemo and Android
- WDT problem solved
- Touchscreen driver compatible with both Maemo and Android (module option to select)
- overclock capable
- nearly all Titan's modules included
- latest bug fixes from Nokia

... just to mention a few.

My plan is to make a initrd image, which includes the bootmenu, kernel modules, and templates to boot both Maemo and Android, without any changes to the existing Maemo system.

anybody interested in trying out my beta kernel?

cheers
jay

I think we'd all like to try this!!!

[Jay-C]

About the watchdog problem...

when N900 is booting up, the NOLO bootloader enables the watchdogs, apparently both OMAP and TWL4030 wdt's.
When the OS is booting up, the watchdogs are still enabled, and assumed to be reseted ASAP. We already have drivers for both watchdogs, but there is a small problem with the twl4030 driver. It does not reset the watchdog when loaded into the kernel.

The fix is simple:

--- linux.orig/drivers/watchdog/twl4030_wdt.c 2010-07-01 18:55:26.870280000 +0100
+++ linux/drivers/watchdog/twl4030_wdt.c 2010-07-01 18:42:23.044153000 +0100
@@ -247,6 +247,9 @@
twl4030_wdt_debugfs, &wdt->poweroff_on_suspend);
#endif
twl4030_wdt_dev = pdev;
+
+ twl4030_wdt_disable(wdt);
+
return 0;
}

And, in Android, just load this module in load_modules.sh.

Cheers
Jay

[dj_steve]

hmm cool, jay-c can you hop into one of the irc rooms would love to try out new kern

[Siggen]

@Jay-C
Okay so if im understanding this right, with your initrd we wont need a separate bootmenu like fanoush's bootmenu?

[e-yes]

Originally Posted by Jay-C

About the watchdog problem...

when N900 is booting up, the NOLO bootloader enables the watchdogs, apparently both OMAP and TWL4030 wdt's.
When the OS is booting up, the watchdogs are still enabled, and assumed to be reseted ASAP. We already have drivers for both watchdogs, but there is a small problem with the twl4030 driver. It does not reset the watchdog when loaded into the kernel.

The fix is simple:


And, in Android, just load this module in load_modules.sh.

Cheers
Jay

dsme && bme already runs on Nitdroid.
also I wrote simple watchdog pinger ('popingui') and it started as service in android (from init.nokia.rc). some watchdog doesn't reset its timeout anyway (I don't remember exactly which one, seems 'external') and system reset occurs. and in my opinion, ought not to disable watchdogs. we ought to fix kernel or userspace problem instead.

in other words: there is no difference in R&D enabled and disabled R&D (with broken watchdogs).

New touchscreen module, "bottom inaccuracies" problem solved (at least for me).

v1 (3450 2900):
http://slil.ru/29420775
MD5: 9dadaf9c9c071dbddc0d9925801b3b2f

v2 (3450 3100):
http://slil.ru/29420842
MD574c79c2e7f50c46ec1a8828668f6a64c
place it in /system/lib/modules

Please report which one works better for you. Thanks.

[Man_Utd_4Ever]

hi everybody
please help me
i always see this error

getbootstate: Invalid selection
Choose bootup option:
2) MMC
9) Start a shell

what i can to do?
i did all srtucture

[maemosboy]

Originally Posted by Man_Utd_4Ever

hi everybody
please help me
i always see this error


what i can to do?
i did all srtucture

Same here.

[M00NB34M]

Originally Posted by maemosboy

Same here.

You need to configure Bootmenu to search for the right partition...im at an airport atm and dont have time to paste the code but in the bootmenu settings file you need to direct the bootmenu to the correct partition (one with android on it...EXT4 on memory card)

Hope this helps

Btw if you jump a few dozen paes back you'll find the code...i THINK Toja pasted it somewhere and a various few others!!