Re: Another Android port: NITdroid
 

AFAICT those keys are for individual applications not for the whole operating system but if you find something interesting please share.

Re: Another Android port: NITdroid
 

The last one... :) Even with the FASTFPE emulation, which probably will speed up the whole 770.

I saw the console file redirection in the kernel config, was just wondering if there is a better way. Can I use the USB to serial convertor and ttyUSB0 to redirect the console output, and more important - how can i receive it :)?

Re: Another Android port: NITdroid
 

You can make the dns persistent by putting it in /default.prop
(/nit/bin/vi /default.prop ... or pull&push)

Re: Another Android port: NITdroid
 

someone booted this up from ext card??? if so, that's why it won't boot when ext-card is in and fs.is on mmcblk0p2 (the internal)...

Re: Another Android port: NITdroid
 

Solca, could you put the Linux kernel 2.6.28 with working WiFi driver online somewhere so we can use it on Maemo as well?

Re: Another Android port: NITdroid
 

Probably not yet usable with Maemo :)

Re: Another Android port: NITdroid
 

try: reboot -p

Re: Another Android port: NITdroid
 

Excellent!

The best way to get console output is via the internal serial ports on the NITs, even you get bootloader output, there is no other best way.

I just solder a tiny cable to the TX pad under the battery, GND can be anything in the chassis and both cables connected to a cheap USB to serial convertor dongle on my desktop/laptop based on the FTDI chip (ftdi_sio.ko driver). One has to be careful to use a dongle that matches the voltage on the NIT (3.3V) if not you fry your NIT. This help me a lot in debugging the initial kernels.

But earlier when I didn't have the serial console setup I just select the mini font for the framebuffer console so I can actually see much more output on the screen. :o

Re: Another Android port: NITdroid
 

Both kernel and driver are already online, the kernel it is the zImage-nitdroid-n8x0 file you download from the NITdroid site and the WiFI driver you can pull it from /system/lib/modules/stlc45xx.ko from the rootfs.

The WiFi driver doesn't work in Maemo because wlancond doesn't speak the mac80211 API so you can't create connections from the GUI although you can make it work from a shell using iwconfig and wpa_supplicant, manually.

Re: Another Android port: NITdroid
 

I'm curious as to why you're using a bleeding edge kernel. What version do already-working Android phones use? It seems that an added variable is unnecessarily being introduced. Or am I missing something? Also, maybe the 2.6.27 Fremantle patches are compatible with Diablo. Do you see where I'm going? My opinion is that you should create a hybrid kernel based on already-running devices.

Does Android use an initfs? If not, maybe it should if it's going to run on Nokia tablets with 2 SDHC slots. Maybe you could more easily capture boot information. You should be able to create a hybrid initfs and bootmenu from the Diablo base. And although we want to be less embedded in the long run, I think talk about a grub-like boot partition is just another vaporware barrier to early usability. Sorry if I'm less informed than I should be; I'm just a proponent of walking before running.