Fw:porting android to omap3 evm

by Nimit Manglick » Wed, 15 Apr 2009 12:38:48 GMT


Sponsored Links
 i Cindy,

1.what do you mean about cupcake branch
Cupcake is the new android branch which has just been merged to master
branch.
Means to say that it is the latest android code drop branch.
So In that currently alsa (for audio support ) is breaking, but first of all
ur basic android should boot.

2.Boot from nfs

Try with the following nfs bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<path to ur filesystem on ur host machine>
,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init

Please make sure you have run all the services like nfs-server etc on ur
host machine
and made a entry in ur /etc/exports

Hope it helps.

Regards
Nimit


2009/4/14 cindy_king_1024 <cindy_king_1...@126.com>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by Nimit Manglick » Thu, 16 Apr 2009 14:08:25 GMT


 i Cindy,

Its the problem in ur filesystem...

and I am not sure about ur booatargs as well....

Please use my bootargs which i mentioned earlier.. The bootargs u r using
that might be specific to beagle board I suppose.

Or else try to boot it via SD / MMC card.

Regards
NImit

2009/4/15 cindy_king_1024 <cindy_king_1...@126.com>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Fw:porting android to omap3 evm

by cindy_king_1024 » Fri, 17 Apr 2009 08:51:22 GMT


 i,Nimit
Thanks for your attention,I know there is something wrong with NFS
filesystem,but I don't know how to modify the init.rc / init.goldfish.rc and
system/bin/init.goldfish.sh.



009-04-16 14:08:18quot;Nimit Manglick" <nimitandr...@gmail.com> Hi Cindy,

Its the problem in ur filesystem...

and I am not sure about ur booatargs as well....

Please use my bootargs which i mentioned earlier.. The bootargs u r using that
might be specific to beagle board I suppose.

Or else try to boot it via SD / MMC card.

Regards
NImit


2009/4/15 cindy_king_1024 <cindy_king_1...@126.com>

Hi Nimit
I enter the command about nfs boott come with the same errorhat about
yoursave you seen such setences

<6>Waiting 2sec before mounting root device...
Waiting 2sec before mounting root device...

<5>Looking up port of RPC 100003/2 on 10.86.76.68
Looking up port of RPC 100003/2 on 10.86.76.68
<5>Looking up port of RPC 100005/1 on 10.86.76.68
Looking up port of RPC 100005/1 on 10.86.76.68

VFS: Mounted root (nfs filesystem).
VFS: Mounted root (nfs filesystem).
<6>Freeing init memory: 144K
Freeing init memory: 144K
<4>Warning: unable to open an initial console.
Warning: unable to open an initial console.
<0>Kernel panic - not syncing: Attempted to kill init!
Kernel panic - not syncing: Attempted to kill init!

the nfs bootargssetenv console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=10.86.76.68:/home/Android_rfs ip=dhcp nolock,rsize=1024,wsize=1024
rootdelay=2 video=omapfb:mode:640x...@50 init=/init mem=128M


Kernel command line: 009-04-15 12:38:36quot;Nimit Manglick"
<nimitandr...@gmail.com>

Hi Cindy,


1.what do you mean about cupcake branch
Cupcake is the new android branch which has just been merged to master branch.
Means to say that it is the latest android code drop branch.
So In that currently alsa (for audio support ) is breaking, but first of all ur
basic android should boot.

2.Boot from nfs

Try with the following nfs bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<path to ur filesystem on ur host machine>
,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init

Please make sure you have run all the services like nfs-server etc on ur host
machine
and made a entry in ur /etc/exports

Hope it helps.

Regards
Nimit



2009/4/14 cindy_king_1024 <cindy_king_1...@126.com>

Dear NimitI'm glad to hear from yous you discript1.what do you mean about cupcake branch
2.Boot from nfs he inviaronment variable was thatsetenv console=ttyS0,115200n8 ip=dhcp rw root=/dev/nfs
nfsroot=10.86.76.92:/home/jennifer/Android_rfs,nolock mem=88M
video=omapfb:mode:640x...@50 init=/init

3.Without the patch to the nfs filesystemt aborted with the following
sentence
IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer from
0.0.0.0, my address is 10.8
6.76.115
my address is 10.86.76.115

IP-Config: Complete:IP-Config: Complete:
device=eth0

device=eth0, addr=10.86.76.115, addr=10.86.76.115, mask=255.255.255.0,
mask=255.255.255.0, gw=1
0.86.76.249, gw=10.86.76.249,
host=10.86.76.115, domain=, nis-domain=(none),
host=10.86.76.115, domain=, nis-domain=(none),

bootserver=0.0.0.0,

bootserver=0.0.0.0, rootserver=10.86.76.92, rootserver=10.86.76.92,
rootpath=, rootpath=

<5>Loo



Fw:porting android to omap3 evm

by cindy_king_1024 » Fri, 17 Apr 2009 09:08:20 GMT


 i,Nimit
Sorry,I have forget .If boot from SD card ,how to make the filesystem? The
content of the SD contain all the things in the NFS filesystem:
data dev init.goldfish.rc sbin system
default.prop init init.rc proc sys


009-04-16 14:08:18quot;Nimit Manglick" <nimitandr...@gmail.com> Hi Cindy,

Its the problem in ur filesystem...

and I am not sure about ur booatargs as well....

Please use my bootargs which i mentioned earlier.. The bootargs u r using that
might be specific to beagle board I suppose.

Or else try to boot it via SD / MMC card.

Regards
NImit


2009/4/15 cindy_king_1024 <cindy_king_1...@126.com>

Hi Nimit
I enter the command about nfs boott come with the same errorhat about
yoursave you seen such setences

<6>Waiting 2sec before mounting root device...
Waiting 2sec before mounting root device...

<5>Looking up port of RPC 100003/2 on 10.86.76.68
Looking up port of RPC 100003/2 on 10.86.76.68
<5>Looking up port of RPC 100005/1 on 10.86.76.68
Looking up port of RPC 100005/1 on 10.86.76.68

VFS: Mounted root (nfs filesystem).
VFS: Mounted root (nfs filesystem).
<6>Freeing init memory: 144K
Freeing init memory: 144K
<4>Warning: unable to open an initial console.
Warning: unable to open an initial console.
<0>Kernel panic - not syncing: Attempted to kill init!
Kernel panic - not syncing: Attempted to kill init!

the nfs bootargssetenv console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=10.86.76.68:/home/Android_rfs ip=dhcp nolock,rsize=1024,wsize=1024
rootdelay=2 video=omapfb:mode:640x...@50 init=/init mem=128M


Kernel command line: 009-04-15 12:38:36quot;Nimit Manglick"
<nimitandr...@gmail.com>

Hi Cindy,


1.what do you mean about cupcake branch
Cupcake is the new android branch which has just been merged to master branch.
Means to say that it is the latest android code drop branch.
So In that currently alsa (for audio support ) is breaking, but first of all ur
basic android should boot.

2.Boot from nfs

Try with the following nfs bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<path to ur filesystem on ur host machine>
,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init

Please make sure you have run all the services like nfs-server etc on ur host
machine
and made a entry in ur /etc/exports

Hope it helps.

Regards
Nimit



2009/4/14 cindy_king_1024 <cindy_king_1...@126.com>

Dear NimitI'm glad to hear from yous you discript1.what do you mean about cupcake branch
2.Boot from nfs he inviaronment variable was thatsetenv console=ttyS0,115200n8 ip=dhcp rw root=/dev/nfs
nfsroot=10.86.76.92:/home/jennifer/Android_rfs,nolock mem=88M
video=omapfb:mode:640x...@50 init=/init

3.Without the patch to the nfs filesystemt aborted with the following
sentence
IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer from
0.0.0.0, my address is 10.8
6.76.115
my address is 10.86.76.115

IP-Config: Complete:IP-Config: Complete:
device=eth0

device=eth0, addr=10.86.76.115, addr=10.86.76.115, mask=255.255.255.0,
mask=255.255.255.0, gw=1
0.86.76.249, gw=10.86.76.249,
host=10.86.76.115, domain=, nis-domain=(none),
host=10.86.76.115, domain=, nis-domain=(none),

bootserver=0.0.0.0,

bootserver=0.0.0.0, rootserver=10.



Fw:porting android to omap3 evm

by Anil Sasidharan » Fri, 17 Apr 2009 12:03:21 GMT


 i,

Android has already been ported to OMAP3EVM from Mistral. In fact
this initiative has been very active for approximately a year. We will be
uploading the demo-images to our public repository. You can visit the URL
http://www.mistralsolutions.com/technology/android_omap.php for more info.

Warm Regards,
Anil

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>:
nolock,rsize=1024,wsize=1024
give
to
from
errno:

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by Nimit Manglick » Fri, 17 Apr 2009 12:42:38 GMT


 i Cindy,

First of all the filesystem which you have used once with nfs cant work
directly on SD / MMC card as once that filesystem has been used on nfs so
while booting android creats so many cache files.

So If u r booting via SD / MMC card then ur SD / MMC card shall be
containing two partitions :- first ext3 (for filesystem) second vfat (for
uImage and media files)

To create a filesystem out of the source follow the steps from this link
under the title (Root file System of Android
<http://labs.embinux.org/index.php?title=Root_file_System_of_Android&action=edit&redlink=1>)
:-

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

You dont need to touch init.goldfish.rc that is emant only for QEMU
emulator.

So you just need to have a look on init.rc. To modify init.rc follow the
steps from the above link only.

So other than that what u want to modify in that ??

Regards
Nimit



2009/4/17 Anil Sasidharan <anil...@gmail.com>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Fri, 17 Apr 2009 19:33:20 GMT


 iNimit
In the links
http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/data/target
ip=192.168.1.1::255.255.255.0 nolock,rsize=1024,wsize=1024 rootdelay=2
video=omapfb:mode:1280x...@50 init=/init
1.what dose the directory mean/data/target meanow does it relate to
Android_rfs

2.Dose it need to write a shell for booting android


009-04-17 12:42:33quot;Nimit Manglick" <nimitandr...@gmail.com>
Hi Cindy,

First of all the filesystem which you have used once with nfs cant work
directly on SD / MMC card as once that filesystem has been used on nfs so while
booting android creats so many cache files.

So If u r booting via SD / MMC card then ur SD / MMC card shall be containing
two partitions :- first ext3 (for filesystem) second vfat (for uImage and media
files)

To create a filesystem out of the source follow the steps from this link under
the title (Root file System of Android ) :-

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

You dont need to touch init.goldfish.rc that is emant only for QEMU emulator.

So you just need to have a look on init.rc. To modify init.rc follow the steps
from the above link only.

So other than that what u want to modify in that ??

Regards
Nimit




2009/4/17 Anil Sasidharan <anil...@gmail.com>
Hi,

Android has already been ported to OMAP3EVM from Mistral. In fact
this initiative has been very active for approximately a year. We will be
uploading the demo-images to our public repository. You can visit the URL
http://www.mistralsolutions.com/technology/android_omap.php for more info.

Warm Regards,
Anil

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>:







--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by Nimit Manglick » Mon, 20 Apr 2009 21:28:46 GMT


 i Cindy,

Dont use these bootargs as these are specifically for beagle.

Use these bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<android root filesysetm path> ,nolock,wsize=1024,rsize=1024 ip=dhcp
init=/init

data/target is the path of the rootfilesystem placed on ur host machine from
where u r mounting the android root filesystem.

2.Dose it need to write a shell for booting android
NO, its not necessary.

Regards
Nimit

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Tue, 21 Apr 2009 00:12:39 GMT


 i,Nimit
I have try the bootargs as you said:

setenv bootargs mem=128M console=ttyS0,115200n8 rw root=/dev/nfs
nfsroot=10.86.76.95:/home/Android_rfs ,nolock, ip=dhcp init=/init
but it always died there:

<5>Looking up port of RPC 100003/2 on 10.86.76.95 Looking up port of RPC
100003/2 on 10.86.76.95 <5>Looking up port of RPC 100005/1 on 10.86.76.95
Looking up port of RPC 100005/1 on 10.86.76.95
VFS: Mounted root (nfs filesystem).
VFS: Mounted root (nfs filesystem).
<6>Freeing init memory: 144K
Freeing init memory: 144K
<0>Kernel panic - not syncing: Attempted to kill init!
Kernel panic - not syncing: Attempted to kill init!




009-04-20 21:28:33quot;Nimit Manglick" <nimitandr...@gmail.com>

Hi Cindy,

Dont use these bootargs as these are specifically for beagle.

Use these bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd root=/dev/nfs rw
nfsroot=10.86.76.95:/home/rootfs,rsize=1024,wsize=1024,nolock ip=dhcp init=/init
But it come with:




data/target is the path of the rootfilesystem placed on ur host machine from
where u r mounting the android root filesystem.

2.Dose it need to write a shell for booting android
NO, its not necessary.

Regards
Nimit



2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>

HiNimit
In the links
http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board


console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/data/target
ip=192.168.1.1::255.255.255.0 nolock,rsize=1024,wsize=1024 rootdelay=2
video=omapfb:mode:1280x...@50 init=/init
1.what dose the directory mean/data/target meanow does it relate to
Android_rfs

2.Dose it need to write a shell for booting android


009-04-17 12:42:33quot;Nimit Manglick" <nimitandr...@gmail.com>
Hi Cindy,

First of all the filesystem which you have used once with nfs cant work
directly on SD / MMC card as once that filesystem has been used on nfs so while
booting android creats so many cache files.

So If u r booting via SD / MMC card then ur SD / MMC card shall be containing
two partitions :- first ext3 (for filesystem) second vfat (for uImage and media
files)

To create a filesystem out of the source follow the steps from this link under
the title (Root file System of Android ) :-

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

You dont need to touch init.goldfish.rc that is emant only for QEMU emulator.

So you just need to have a look on init.rc. To modify init.rc follow the steps
from the above link only.

So other than that what u want to modify in that ??

Regards
Nimit




2009/4/17 Anil Sasidharan <anil...@gmail.com>
Hi,

Android has already been ported to OMAP3EVM from Mistral. In fact
this initiative has been very active for approximately a year. We will be
uploading the demo-images to our public repository. You can visit the URL
http://www.mistralsolutions.com/technology/android_omap.php for more info.

Warm Regards,
Anil

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>:











--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by sathish kumar » Tue, 21 Apr 2009 13:21:25 GMT


 i,
Here is my bootatgs and it is not working although it is asper your
bootargs.

bootargs=root=/dev/nfs mem=128M netdev=27,0,0xfc800000,0xfc800010,eth0
ip=192.168.0.212:192.168.0.212
nfsroot=192.168.0.118:/mnt/venu_fs,rsize=1024,wsize=1024
console=ttyAMA0 cachepolicy=writealloc
but still i get
Kernel panic - not syncing: Attempted to kill init!

sathish


2009/4/20 Nimit Manglick <nimitandr...@gmail.com>


--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Tue, 21 Apr 2009 14:18:24 GMT


 i,Nimit
My android source without cupcake baranch that you say above.
1.when compile android ,dose it need to add alsa-lib and alsa_sound with the
patch Alsa_sound-v1.1.patch.
2. In the filesystem ,is it need to patch Initrc.patch and Qwerty.patch


3.Can you show me the config file of you kernel(wersion?),mine reference to the
links:

http://labs.embinux.org/git/cgit.cgi/linux-omap-2.6/commit/?h=evm-android-2.6.27


009-04-20 21:28:33quot;Nimit Manglick" <nimitandr...@gmail.com> Hi Cindy,

Dont use these bootargs as these are specifically for beagle.

Use these bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<android root filesysetm path> ,nolock,wsize=1024,rsize=1024 ip=dhcp
init=/init

data/target is the path of the rootfilesystem placed on ur host machine from
where u r mounting the android root filesystem.

2.Dose it need to write a shell for booting android
NO, its not necessary.

Regards
Nimit


2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>

HiNimit
In the links
http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board


console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/data/target
ip=192.168.1.1::255.255.255.0 nolock,rsize=1024,wsize=1024 rootdelay=2
video=omapfb:mode:1280x...@50 init=/init
1.what dose the directory mean/data/target meanow does it relate to
Android_rfs

2.Dose it need to write a shell for booting android


009-04-17 12:42:33quot;Nimit Manglick" <nimitandr...@gmail.com>
Hi Cindy,

First of all the filesystem which you have used once with nfs cant work
directly on SD / MMC card as once that filesystem has been used on nfs so while
booting android creats so many cache files.

So If u r booting via SD / MMC card then ur SD / MMC card shall be containing
two partitions :- first ext3 (for filesystem) second vfat (for uImage and media
files)

To create a filesystem out of the source follow the steps from this link under
the title (Root file System of Android ) :-

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

You dont need to touch init.goldfish.rc that is emant only for QEMU emulator.

So you just need to have a look on init.rc. To modify init.rc follow the steps
from the above link only.

So other than that what u want to modify in that ??

Regards
Nimit




2009/4/17 Anil Sasidharan <anil...@gmail.com>
Hi,

Android has already been ported to OMAP3EVM from Mistral. In fact
this initiative has been very active for approximately a year. We will be
uploading the demo-images to our public repository. You can visit the URL
http://www.mistralsolutions.com/technology/android_omap.php for more info.

Warm Regards,
Anil

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>:











--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by Rupesh Gujare » Tue, 21 Apr 2009 14:41:45 GMT


 Cindy,



No You do not need this.
You need apply Initrc.patch,(most probably this patch will solve your
current error) Qwerty.patch is of no use to you.
Above defconfig is working fine. You can go ahead with it.

Regards,

-- 
Rupesh Gujare
 http://embinux.com 



--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Tue, 21 Apr 2009 15:21:33 GMT


 ake sure adding the patch correctly(Tls.patch and Gl_wrapper.patch):

until it come with:
patching file <patchfile>


009-04-21 13:21:19quot;sathish kumar" <sathish...@gmail.com>
Hi,
Here is my bootatgs and it is not working although it is asper your bootargs.

bootargs=root=/dev/nfs mem=128M netdev=27,0,0xfc800000,0xfc800010,eth0
ip=192.168.0.212:192.168.0.212
nfsroot=192.168.0.118:/mnt/venu_fs,rsize=1024,wsize=1024 console=ttyAMA0
cachepolicy=writealloc

but still i get
Kernel panic - not syncing: Attempted to kill init!

sathish



2009/4/20 Nimit Manglick <nimitandr...@gmail.com>
Hi Cindy,

Dont use these bootargs as these are specifically for beagle.

Use these bootargs :-

setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs
nfsroot=<android root filesysetm path> ,nolock,wsize=1024,rsize=1024 ip=dhcp
init=/init

data/target is the path of the rootfilesystem placed on ur host machine from
where u r mounting the android root filesystem.

2.Dose it need to write a shell for booting android
NO, its not necessary.

Regards
Nimit


2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>

HiNimit
In the links
http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board


console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/data/target
ip=192.168.1.1::255.255.255.0 nolock,rsize=1024,wsize=1024 rootdelay=2
video=omapfb:mode:1280x...@50 init=/init
1.what dose the directory mean/data/target meanow does it relate to
Android_rfs

2.Dose it need to write a shell for booting android


009-04-17 12:42:33quot;Nimit Manglick" <nimitandr...@gmail.com>
Hi Cindy,

First of all the filesystem which you have used once with nfs cant work
directly on SD / MMC card as once that filesystem has been used on nfs so while
booting android creats so many cache files.

So If u r booting via SD / MMC card then ur SD / MMC card shall be containing
two partitions :- first ext3 (for filesystem) second vfat (for uImage and media
files)

To create a filesystem out of the source follow the steps from this link under
the title (Root file System of Android ) :-

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

You dont need to touch init.goldfish.rc that is emant only for QEMU emulator.

So you just need to have a look on init.rc. To modify init.rc follow the steps
from the above link only.

So other than that what u want to modify in that ??

Regards
Nimit




2009/4/17 Anil Sasidharan <anil...@gmail.com>
Hi,

Android has already been ported to OMAP3EVM from Mistral. In fact
this initiative has been very active for approximately a year. We will be
uploading the demo-images to our public repository. You can visit the URL
http://www.mistralsolutions.com/technology/android_omap.php for more info.

Warm Regards,
Anil

2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>:












--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Tue, 21 Apr 2009 15:24:03 GMT


 009-04-21 14:41:31quot;Rupesh Gujare" <rupesh.guj...@embinux.com> Cindy,



Hi,Nimit
My android source without cupcake baranch that you say above.
1.when compile android ,dose it need to add alsa-lib and alsa_sound with the 
patch Alsa_sound-v1.1.patch.
No You do not need this.

2. In the filesystem ,is it need to patch  Initrc.patch and Qwerty.patch


You need apply Initrc.patch,(most probably this patch will solve your current 
error) Qwerty.patch is of no use to you.

3.Can you show me the config file of you kernel(wersion?),mine reference to the 
links:

 http://labs.embinux.org/git/cgit.cgi/linux-omap-2.6/commit/?h=evm-android-2.6.27 

Above defconfig is working fine. You can go ahead with it.

Regards,

-- 
Rupesh Gujare
 http://embinux.com 




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Fw:porting android to omap3 evm

by cindy_king_1024 » Tue, 21 Apr 2009 15:29:11 GMT


 Thanks,but I have a question :
In your answer :
1.when compile android ,dose it need to add alsa-lib and alsa_sound with the 
patch Alsa_sound-v1.1.patch.
No You do not need this.
You mean I need not add the patch or I need not add alsa-lib and alsa_sound?
All of alsa-lib and slsa_sound is not needed?



009-04-21 14:41:31quot;Rupesh Gujare" <rupesh.guj...@embinux.com> Cindy,



Hi,Nimit
My android source without cupcake baranch that you say above.
1.when compile android ,dose it need to add alsa-lib and alsa_sound with the 
patch Alsa_sound-v1.1.patch.
No You do not need this.

2. In the filesystem ,is it need to patch  Initrc.patch and Qwerty.patch


You need apply Initrc.patch,(most probably this patch will solve your current 
error) Qwerty.patch is of no use to you.

3.Can you show me the config file of you kernel(wersion?),mine reference to the 
links:

 http://labs.embinux.org/git/cgit.cgi/linux-omap-2.6/commit/?h=evm-android-2.6.27 

Above defconfig is working fine. You can go ahead with it.

Regards,

-- 
Rupesh Gujare
 http://embinux.com 




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. problem in services

Hello frnds.....

I am presently working on services.I have read many articles related
to services.But one thing I dont understand is if we want our
application to run in background how can we implement services without
using Activities.......

Urgent help needed

Thanks
Nemat
--~--~---------~--~----~------------~-------~--~----~

2. Multitouch: Two buttons at the same time?

Hi, I'm planning to develop a small jump and run game and wondered how
to recognize two button presses at one time. For example, I want to
run left and jump during running. Is it possible to catch both button
presses on the touch?

Regards, Florian

--~--~---------~--~----~------------~-------~--~----~

3. Android Game Framework ?

4. Google Checkout API for Android application

5. Problem involving emulators and networking.

6. Overlay on MapView

7. RotateAnimation modifying ImageView