Hi Ananth, Thanks,It was working for me. Will it possible for you to upload the samsung + android patch you have applied to the stock linux 2.6.25 kernel ? or can u explain how you upgraded the kernel to 2.6.25.Only samsung linux kernel 2.6.21.5 is getting booted up on this board other than yours.Can u guide me on this
On Jan 21, 3:08 pm, Ananth M <[email protected]> wrote: > Hi Praveen, > > Are you able to get the Android Screen on your Board using the my > Kernel Image and File system? > > Regards > Ananth > > On 1/21/09, Praveen <[email protected]> wrote: > > > > > Hi Ananth, > > > Thanks for all your help.Can you please upload the samsung + android > > patches you have applied to the 2.6.25 linux kernel to get it booted > > up on smdk6400? > > > On Jan 20, 1:34 pm, "Ananth M" <[email protected]> wrote: > >> Hi Abhishek > >> Today I uploaded the kernel and file systems that I am using to my > >> website. > >> I created a blog also in the same website. ( this is my first blog, > >> so forgive me if there is any mistakes ) > >> The blog is at : > >> http://mekaananth.synthasite.com/android-onto-smdk6400.php > > >> Please let me know for any help or issues > > >> Regards > >> Ajay > > >> On 1/20/09, sumit <[email protected]> wrote: > > >> > hi Ajay > > >> > I had interacted with you about porting Android in smdk6400 and found > >> > your suggestions useful. I have gone through your recent posting and > >> > found that you have successfully ported the kernel and file system > >> > onto the board.Congratulations. > > >> > In our porting affort, I am facing the issue that zimage does not boot > >> > where as image starts booting. I checked through zImage booting > >> > sequence and found that arch/arm/boot/head.S is the first file which > >> > gets executed. This file has ATAG structure (which I guess is for > >> > passing parameters from boot loader to the kernel). I am using the > >> > 2.6.23 kernel and bootloader is uboot 1.1.6. I suspect the problem is > >> > with uboot configuration (which was built to handle kernel version > >> > 2.6.21 was not handling ATAG though uboot 1.1.1 has support for > >> > ATAG) . Please let me know if this thinking is correct and your > >> > suggestions on sorting out the problem. > > >> > And I also want to know if the file system from new Android 1.0 sdk > >> > will support 2.6.23 kernel . > > >> > regards > > >> > Abhishek > > >> > On Dec 11 2008, 11:07 am, ajay <[email protected]> wrote: > >> >> Hi All > > >> >> I ported the Android-mc14 and Android-mc20 onto s3c6400 earlier. > > >> >> Currently I am poritng the Android1.0 on to the same Board with > >> >> the following config: > >> >> - Kernel : Linux-2.6.25 > >> >> - File systems : Taken from the Android 1.0 > > >> >> The Board is booted properly and the initial screen is displayed. > > >> >> Now my problem is that the initial screen is the screen with > >> >> "Andrid " > >> >> "11:25 AM " > >> >> " Charging 100 %" > >> >> "Screen Locked > >> >> (Press Menu to unlock the screen" > > >> >> Since the board is booted without any SKIN's , I do not have > >> >> the Menu button to unlock the screen. > > >> >> 1) Is it possible to boot the board with SKIN's ? > >> >> 2) Is it possible to by-pass this screen-lock screen ? > > >> >> 3) In the emulator of Android1.0, if we start the emulator with "- > >> >> noskin" option , you will get the same screen. ( i.e without any menu > >> >> button". In that case, how can the user un-locks the screen ? > > >> >> Can anyone provide some information regarding this ? > > >> >> Thank you > >> >> RegardsAjay --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
