Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Nishanth Menon wrote:
Looping in OMAP ML to the good news..
Congrats!
sim0nx said the following on 04/05/2008 06:35 AM:
I can't believe it !!!
Android runs on the maemo n810 !!!
Great!
Do you have some screenshots we can add to
http://elinux.org/Android_on_OMAP#Screenshots
?
Anything else we should add/correct at
http://elinux.org/Android_on_OMAP
?
Thanks
Dirk
Btw: Do you have any power management issues like
http://elinux.org/Android_on_OMAP#Power_management
? We still don't know anything about them :(
After reading this:
http://groups.google.lu/group/android-internals/browse_thread/thread/93570c41bce07f16?hl=en
for the 100th time, and following the instructions on the mentioned
link:
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
it works.
Here are the specifics I've implemented:
* patch /etc/init.rc
begin : init.rc
## qemu-init {
## exec /etc/qemu-init.sh
## }
network-property {
exec /etc/set_network.sh
}
/bin/chmod -R a+rw /data /tmp
/bin/chmod a+rw .
/bin/chmod -R a+rw data
# rm /dev/log (if you have)
# mkdir /dev/log;touch /dev/log/{main,events,radio}
* you can see usefull infos from strace log and /dev/log/main
and instead of:
chroot . /a.sh
I execute the android init process:
chroot . /init
Not sure yet what exactly of those steps solved the problem (maybe the
qemu one), but it does work.
After a quick try I see that the touchscreen doesn't work (the
keyboard does though), but that shouldn't be too hard to fix.
BTW, this is using an m5 kernel, and binder.c
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Android
Internals group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-internals?hl=en
-~--~~~~--~~--~--~---
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Congrats. Has anyone had any luck getting a 2.6.23 or 2.6.24 kernel working with the 800 or 810? When I was poking around with it a while back, I had to backport our stuff to .21 due to binary-only wifi drivers being incompatible with newer kernels. Also, if anyone knows of work done to figure out how the battery charge control, etc works on the 800/810 hardware, I'm highly curious. Have not had the spare time to reverse engineer that stuff and if somebody's already done the hard work, so much the better. Brian [Nishanth Menon [EMAIL PROTECTED]] Looping in OMAP ML to the good news.. Congrats! sim0nx said the following on 04/05/2008 06:35 AM: I can't believe it !!! Android runs on the maemo n810 !!! After reading this: http://groups.google.lu/group/android-internals/browse_thread/thread/93570c41bce07f16?hl=en for the 100th time, and following the instructions on the mentioned link: http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html it works. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
[Georges Toth [EMAIL PROTECTED]] The touchscreen doesn't work yet, but I hope we can figure that out too. - The driver works, there is output when one does a cat on /dev/input/event3, but android doesn't recognize it. Some buttons don't work ... wrong mapping. If anybody has an idea how to see what keycodes certain buttons are bound to and how to edit the mapping in android that would be great :-). Here's a brute force approach to sorting out input events: run getevent on the emulator and on the target hardware and compare the results. It's in /system/bin. I believe the touchpad issue has to do with sending events that the system recognizes as pen down and pen up events. Haven't looked at this in a while. Keylayouts live in /system/usr/keylayout/*.kl and are used to translate from the raw input event codes to android keycodes. Keymaps live in /system/user/keychars/*.kcm.bin (undocumented binary format right now, sorry) and are used to describe how the key events and modifiers and such are related. Brian -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Hi, Great! Do you have some screenshots we can add to http://elinux.org/Android_on_OMAP#Screenshots ? I've added 3 screenshots on that page :-) Anything else we should add/correct at http://elinux.org/Android_on_OMAP ? I wanted to add some instructions for the maemo once I got it fully working :-). Basically the differences from the wiki I had to use are: - m3 or m5 kernel, but using binder.c in any case (not the original binder code from m3) - backport the android patch, to the nokia kernel sources (2.6.21) - use the android init instead of the mentioned a.sh script - edit the init configuration and comment the qemu parts - only the m3 userspace files currently work The touchscreen doesn't work yet, but I hope we can figure that out too. - The driver works, there is output when one does a cat on /dev/input/event3, but android doesn't recognize it. Some buttons don't work ... wrong mapping. If anybody has an idea how to see what keycodes certain buttons are bound to and how to edit the mapping in android that would be great :-). Btw: Do you have any power management issues like http://elinux.org/Android_on_OMAP#Power_management ? We still don't know anything about them :( No. It's just that the display rather quickly dims and shuts down (2-4s to dim, and another 2 secs to shutdown). It doesn't work to shut the display down via the android menu, and android doesn't display the battery status. Besides that there are no problems. -- regards, Georges Toth -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: source.mvista links are broken
Kevin Hilman wrote: Tony Lindgren [EMAIL PROTECTED] writes: * Iqbal [EMAIL PROTECTED] [080404 13:07]: Looks like the OMAP tree links are broken and the summary,short log and other fields don't work. http://source.mvista.com/git/?p=linux-omap-2.6.git;a=commit;h=8a88c221c88399bc694c367dbea01ffc4153ef20 Yeah, I've noticed that too. Probably git needs updating on source.mvista.com, it seems to have issues with reading packed objects. I've fixed it to some extent by scp'ing over some object files, and then there was a brief file permissions problem too... In any case, please use the kernel.org instead: http://git.kernel.org/git/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git I've notified Kevin about the issue, so we probably have to wait for git to get updated. git on source.mvista.com is now updated to 1.5.4.5. Let me know if there are any more problems. omap-git git version git version 1.5.4.5 omap-git cg-version cogito-0.18.2 omap-git cat .git/HEAD 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d omap-git cat .git/branches/origin git://source.mvista.com/git/linux-omap-2.6 omap-git cg-update origin Recovering from a previously interrupted fetch... Fetching pack (head and objects)... error: refs/heads/origin does not point to a valid object! error: refs/heads/origin does not point to a valid object! remote: Total 0 (delta 0), reused 0 (delta 0) remote: aborting due to possible repository corruption on the remote side. error: waitpid (async) failed fatal: error in sideband demultiplexer cg-fetch: fetching pack failed omap-git Switching to git.kernel.org works: omap-git cat .git/branches/origin git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-git cg-update origin Recovering from a previously interrupted fetch... Fetching pack (head and objects)... error: refs/heads/origin does not point to a valid object! error: refs/heads/origin does not point to a valid object! remote: Counting objects: 896, done. remote: Compressing objects: 100% (490/490), done. remote: Total 896 (delta 453), reused 848 (delta 405) Receiving objects: 100% (896/896), 1.53 MiB | 108 KiB/s, done. Resolving deltas: 100% (453/453), done. Fetching tags... Missing tag v2.6.25-rc8... remote: Counting objects: 1, done. remote: Total 1 (delta 0), reused 1 (delta 0) Unpacking objects: 100% (1/1), done. Up to date. Applying changes... Fast-forwarding 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d - 722c80b23c0d53c16467e35ea43741c597bfbba3 on top of 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d ... omap-git Seems that there is still something broken with MV git? Dirk -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Brian Swetland wrote: [Georges Toth [EMAIL PROTECTED]] The touchscreen doesn't work yet, but I hope we can figure that out too. - The driver works, there is output when one does a cat on /dev/input/event3, but android doesn't recognize it. Some buttons don't work ... wrong mapping. If anybody has an idea how to see what keycodes certain buttons are bound to and how to edit the mapping in android that would be great :-). Here's a brute force approach to sorting out input events: run getevent on the emulator and on the target hardware and compare the results. It's in /system/bin. I believe the touchpad issue has to do with sending events that the system recognizes as pen down and pen up events. Haven't looked at this in a while. Thanks for the tip, I'll have a look at that. Keylayouts live in /system/usr/keylayout/*.kl and are used to translate from the raw input event codes to android keycodes. Keymaps live in /system/user/keychars/*.kcm.bin (undocumented binary format right now, sorry) and are used to describe how the key events and modifiers and such are related. I would need to add/change the event code for the DPAD_CENTER event. Do you perhaps know of a simple way of seeing what code a certain button generates ? -- regards, Georges Toth -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
Hi, Fortunately the userspace can partially ignore the charging issue because the RETU (now Betty) chip takes care of that in the hardware. Charging / charger-cable / power-button / battery-life states are readable from /sys and /dev. Hmm where exactly can you read that info from ? I quickly searched through sysfs, proc and dev but without much luck :-) The best bet for a distro is probably to leave the maemo initfs, which contains closed-source DSME / BME / flasher, in place and let the custom rootfs run on top of it. If you need some details about retu / tahvo driving / bootloading, I may be able to tell because I recently had to poke on it for a different project. Should I get android to work correctly it would be nice to automatically start android after booting the n810. Thus if you have any info on setting up wifi automatically from a script and what exactly to disable to prevent the system from starting Xomap, dbus, hal etc... that would be nice :-) Next would be to try to get the framebuffer driver hacked to work with the m5 image ... the framebuffer driver doesn't support double buffering thus we only get a black screen :-( I understand the userspace is going to be open-source at some point, which would render this work a bit useless. If it doesn't get open-sourced then it's a waste of time either way I think? According to what I've read so far it will be open-sourced as soon as the first devices start to appear...which probably won't be anytime soon But even then that work wouldn't be useless because Google won't release a framebuffer driver for Nokia n800/810 ... so if one wants to be able to run m5 and future releases, somebody has to modify the current driver to be compatible with android...if that is even possible. -- regards, Georges Toth -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [android-internals] Re: Android on Nokia n810 (OMAP2420)
[andrzej zaborowski [EMAIL PROTECTED]] Poky (pokylinux.org) and mamona both work pretty well for everyday use on the nseries. Fortunately the userspace can partially ignore the charging issue because the RETU (now Betty) chip takes care of that in the hardware. Charging / charger-cable / power-button / battery-life states are readable from /sys and /dev. Ah, interesting. When I was looking at the nokia patches to 2.6.21 it seemed like all power control happened from the userspace side and the retu driver just allowed userspace to read/write the chip. Does this patches beyond kernel-source-rx-34_2.6.21.0-osso71.diff.gz? Where would I be looking in /sys or /dev for the charger/battery state? Thanks, Brian -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
