Hi,
finally i got android runs. i port lowmemorykiller and binder.
btw, touchscreen and network not been tested yet.
thanks to you all,
regards,
ruckuus

On Mar 27, 1:44 pm, ruckuus <[EMAIL PROTECTED]> wrote:
> Hi,
> i follow that links, finaly i successfully got android shell
>
> # init: HOW ARE YOU GENTLEMEN
> init: reading config file
> init: device init
> init: mtd partition -1,
> init: mtd partition 0, "U-Boot"
> init: mtd partition 1, "Env"
> init: mtd partition 2, "Kernel"
> init: mtd partition 3, "Rootfs"
> init: mtd partition 4, "Kernel
> sh: can't access tty; job control turned off
> #
> # binder_open(c6561a40 c06e8bc0) (pid 1905) got c5855000
> binder_open(c6561a40 c5f4c540) (pid 2717) got c2662000
> binder_open(c6561a40 c05558e0) (pid 2754) got c14cb000
> binder_open(c6561a40 c05554e0) (pid 2752) got c1535000
> binder_open(c6561a40 c6630160) (pid 2764) got c110c000
> binder_open(c6561a40 c6615a40) (pid 2310) got c11e1000
>
> i try to ssh to OSELAS (which is running OS i use)
> $ ps -ef
> root         1     0  0 02:26 ?        00:00:01 init
> root         2     1  0 02:26 ?        00:00:00 [ksoftirqd/0]
> root         3     1  0 02:26 ?        00:00:00 [events/0]
> root         4     1  0 02:26 ?        00:00:00 [khelper]
> root         5     1  0 02:26 ?        00:00:00 [kthread]
> root        54     5  0 02:26 ?        00:00:00 [kblockd/0]
> root        55     5  0 02:26 ?        00:00:00 [cqueue/0]
> root        57     5  0 02:26 ?        00:00:00 [mxc_spi.1]
> root        60     5  0 02:26 ?        00:00:00 [ksuspend_usbd]
> root        63     5  0 02:26 ?        00:00:00 [khubd]
> root        98     5  0 02:26 ?        00:00:00 [pdflush]
> root        99     5  0 02:26 ?        00:00:00 [pdflush]
> root       100     5  0 02:26 ?        00:00:00 [kswapd0]
> root       101     5  0 02:26 ?        00:00:00 [aio/0]
> root       727     1  0 02:26 ?        00:00:00 [mtdblockd]
> root       752     5  0 02:26 ?        00:00:00 [w1_control]
> root       779     5  0 02:26 ?        00:00:00 [kmmcd]
> root       784     1  0 02:26 ?        00:00:00 [mmcqd]
> root       802     1  0 02:26 ?        00:00:00 [mxc_ts]
> root       803     1  0 02:26 ?        00:00:00 [jffs2_gcd_mtd3]
> root       831     1  0 02:26 ?        00:00:03 /sbin/udevd --daemon
> root      1710     5  0 02:26 ?        00:00:00 [pccardd]
> root      1715     1  0 02:26 ?        00:00:00 /sbin/syslogd
> root      1719     1  0 02:26 ?        00:00:00 /sbin/klogd
> root      1764     1  0 02:26 ?        00:00:00 /usr/sbin/telnetd
> root      1772     1  0 02:26 ?        00:00:00 pure-ftpd
> (SERVER)
> www       1784     1  0 02:26 ?        00:00:00 /usr/sbin/thttpd -d /
> var/www -u www -nor -nos -p 80 -c **.cgi -i /var/run/tht
> root      1807     1  0 02:26 ?        00:00:00 /usr/sbin/sshd
> root      1814     1  0 02:26 ttymxc0  00:00:00 -sh
> root      1826  1814  0 02:27 ttymxc0  00:00:00 /bin/sh ./android-.sh
> root      1828     5  0 02:27 ?        00:00:00 [loop0]
> root      1832  1826  0 02:27 ttymxc0  00:00:00 /system/bin/sh /a.sh
> root      1836  1832  0 02:27 ?        00:00:00 /init
> root      1837  1832  0 02:27 ttymxc0  00:00:00 /system/bin/sh
> root      1874  1836  0 02:27 ?        00:00:00 /system/bin/sh
> root      1881  1836  0 02:27 ?        00:00:00 /system/bin/adbd
> root      1882  1836  0 02:27 ?        00:00:00 /system/bin/usbd -r
> root      1883  1836  0 02:27 ?        00:00:00 /system/bin/debuggerd
> root      1884  1836  0 02:27 ?        00:00:00 /system/bin/rild -l /
> system/lib/libreference-ril.so -- -d /dev/smd0
> root      1904  1836  0 02:27 ?        00:00:00
> zygote                  -Xzygote /system/bin --zygote
> root      1905  1836  0 02:27 ?        00:00:00 /system/bin/runtime
> 2000      1907  1836  0 02:27 ?        00:00:00 /system/bin/dbus-
> daemon --system --nofork
> root      2717  1904  0 02:27 ?        00:00:01
> system_server
> 10004     2752  1904  0 02:27 ?        00:00:00
> com.google.android.home
> 1001      2754  1904  0 02:27 ?        00:00:00
> com.google.android.phone
> 10000     2764  1904  0 02:27 ?        00:00:00
> com.google.process.content
> root      2908  1807  1 02:37 ?        00:00:00 sshd: [EMAIL PROTECTED]/0
> root      2913  2908  0 02:37 pts/0    00:00:00 -sh
> root      2927  2913  0 02:37 pts/0    00:00:00 ps -ef
>
> the android specific process seems running.
>
> i follow steps fromhttp://androidzaurus.seesaa.net/article/80102284.html
> and use android image from 
> :http://androidzaurus.up.seesaa.net/image/android-sdboot-image.tar.gz
>
> as my flash capacity is lower than android image's size, i just boot
> it from SDCARD.
>
> Best Regards,
> Ruckuus
>
> On Mar 27, 8:13 am, kojiran <[EMAIL PROTECTED]> wrote:
>
> > Hi.
>
> > Please try this.
>
> >http://202.165.105.226/babelfish/translate_url_content?lp=ja_en&trurl...
>
> > Best Regards.
>
> > On 3月26日, 午後8:51, ruckuus <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > i follow the link you gave. there is differences between binder.c from
> > > android source and from the patch.
>
> > > is that because of data structure used in different kernel version ?
> > > means between android source and 2.6.18-at kernel ? but i just
> > > compiled after applying patch and i got errors, in the patch file
> > > there is:
>
> > > line 244:
> > > fbi->fix.smem_start + (fbi->fix.line_length * fbi->var.yres),[MISSING
> > > PARAMETER],0, 0);
> > > there's supposed to be [MISSING PARAMETER], what is that ?
>
> > > the screen does not show anything but only blue and pink.
> > > and also i wonder, whether binder driver is built or not, as i
> > > modprobe binder there is no binder module in running kernel. the
> > > kernel is running well but i did not install android image, i used
> > > OSELAS as well.
> > > would you please give me solution to this ?
> > > regards,
> > > Ruckuus
>
> > > On Mar 24, 11:17 am, kojiran <[EMAIL PROTECTED]> wrote:> Hi.
>
> > > > A patch file distributing it to by this article may be just usable.
>
> > > >http://202.165.105.226/babelfish/translate_url_content?.intl=cn&lp=ja...
>
> > > > This is a patch to do porting of Android in iMX31 of linux-2.6.18.
> > > > Also the problem that a screen flickers seems to be fixed.
>
> > > > *Armadillo-500 is a iMX31 (freescale CPU) board.
>
> > > > Best Regards.
>
> > > > On 3月24日, 午後12:21, ruckuus <[EMAIL PROTECTED]> wrote:
>
> > > > > Hi,
> > > > > i use PHYTEC iMX31 (freescale CPU) board. it only supports 2.6.19
> > > > > version.
> > > > > they don't release latest BSP to the kernel version yet. So that,
> > > > > porting android to it's kernel
> > > > > seems simpler than upgrade it's kernel.
> > > > > any suggestion will greatly appreciated.
> > > > > Regards,
> > > > > Ruckuus
>
> > > > > On Mar 19, 8:56 pm, Akio <[EMAIL PROTECTED]> wrote:
>
> > > > > > Hi, ruckuus:
>
> > > > > >          Could you tell me which cpu you use?
> > > > > >          if mx27, as I know you should update to bsp 20071219.
> > > > > >          This is my experience.
>
> > > > > > Best Regards,
> > > > > > Akio
>
> > > > > > On 3月19日, 上午10時44分, ruckuus <[EMAIL PROTECTED]> wrote:
>
> > > > > > > Hi,
> > > > > > > Is there any 2.6.19 android kernel version ? i am using 2.6.19.2
> > > > > > > kernel version (only this version running well with my board not 
> > > > > > > yet
> > > > > > > any update from its vendor). I tried to patch this kernel manually
> > > > > > > regarding to android.diff from benno.
>
> > > > > > > which is the best ?
> > > > > > > 1. upgrade it's kernel version to 2.6.22/23
> > > > > > > 2. patch the kernel to meet android requirements (binder,
> > > > > > > lowmemorykiller, etc.)
>
> > > > > > > Please let me know. Any appreciation will greatly appreciated.
> > > > > > > -ruckuus-
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to