HI,lim!
I compiled your kernel with the tool chain you have provided and got
the kernel Image. I tried to boot the smdk6400 board, but it hangs
after uncompressing the kernel . can you provide any help on this
issue?

I hope you can help me !

I only have s3c6400 board !

Thanks!

On 1月24日, 下午2时23分, leemgs <lee...@gmail.com> wrote:
> Hi,
>
> Sorry, I can't often use internet access  because My status is
> business trip for LCA 2009 currently.
>
> I don't working  forSMDK6400Target the more as I wrote at previous email.
> I am working  android kernel task for SMDK6410 currently.
>
> And. I moved git & bug website  for SMDK6410 from kandroid.org to intomail.net
> because kandroid.org network speed is unstable.
>
> Before)http://www.kandroid.org/git
> After   )http://www.intomail.net/git
>
> Thanks,
> Lim,GeunSik.
>
> 2009/1/22 Praveen <praveendr...@gmail.com>:
>
>
>
> > Hi Lim,
> > I compiled your kernel with the tool chain you have provided and got
> > the kernel Image. I tried to boot thesmdk6400board, but it hangs
> > after uncompressing the kernel . can you provide any help on this
> > issue?
>
> > On Jan 14, 7:23 am, leemgs <lee...@gmail.com> wrote:
> >> Hi, R.wen
>
> >> I stoped  working of android platform  for s3c6400.
> >> But, If you are using s3c6400 core, Please get  synchronize with
> >> "samsung-s3c6410-1-android.1.0" tag
>
> >> I will work  only s3c6410 ( arm 1176 core ) continually,
> >> because our community  don't have 6400 and 6400 core is temp board for
> >> 6410 core.
>
> >> After all,
> >> If you can, I recommend that you will change core from 6400 to 6410..
>
> >> Thanks,
> >> Lim,GeunSik.
>
> >> 2009/1/14 R.wen <rwen2...@gmail.com>:
>
> >> > Dear, Leemgs,
>
> >> >   Thanks for your reply,
> >> > by the way, does thesmdk6400work now?
>
> >> > Yours,
> >> > R.wen
>
> >> > On Jan 14, 9:54 am, leemgs <lee...@gmail.com> wrote:
> >> >> Hi,
>
> >> >> At first, visit tohttp://www/kandroid.org/website.
>
> >> >> I changed project name  form "samsung-s3c64X0-android.1.0" to
> >> >> "samsung-s3c6410-android.1.0".
>
> >> >> Have nice day..
>
> >> >> Thanks,
> >> >> Lim,GeunSik
>
> >> >> 2009/1/14 R.wen <rwen2...@gmail.com>:
>
> >> >> > HI,
>
> >> >> > $git clone git://www.kandroid.org/samsung-s3c64X0-android.1.0
> >> >> > Initialized empty Git repository in 
> >> >> > /home/rwen/samsung-s3c64X0-android.
> >> >> > 1.0/.git/
> >> >> > fatal: The remote end hung up unexpectedly
> >> >> > fetch-pack from 'git://www.kandroid.org/samsung-s3c64X0-android.1.0'
> >> >> > failed.
>
> >> >> > it seems something wrong.
>
> >> >> > R.wen
>
> >> >> > On Jan 12, 7:38 pm, leemgs <lee...@gmail.com> wrote:
> >> >> >> Hi, Praveen
>
> >> >> >> Recently, I moved core support from 6400/6410 to 6410
> >> >> >> because  s3c6400 core is temp age in fact....
>
> >> >> >> So,If you are using s3c6400 core ,
> >> >> >>  I write quick how to for s3c(=smdk)6400 core like you.
>
> >> >> >> Fedora9$> cd /opt
> >> >> >> Fedora9$> 
> >> >> >> wgethttp://www.kandroid.org/~open/devtools/kandroid-1.1.2.1-20080530.glib...
> >> >> >> Fedora9$> tar xzf ./kandroid-1.1.2.1-20080530.glibc.tgz
> >> >> >> Fedora9$> cd ./kandroid-1.1.2.1-20080530.glibc/bin/
> >> >> >> Fedora9$> ls ../bin/arm* -al
>
> >> >> >> Fedora9$> git clone 
> >> >> >> git://www.kandroid.org/samsung-s3c64X0-android.1.0
> >> >> >> Fedora9$> cd samsung-s3c64X0-android.1.0
> >> >> >> Feodra9$> git tag
> >> >> >> Fedora9$> get reset --hard samsung-s3c6410-1-android.1.0
> >> >> >> Fedora9$> cp ./arch/arm/configs/smdk6400mtd_defconfig ./.config
> >> >> >> Feodra9$> make menuconfig
> >> >> >>                   Disable or Enable kernel features that you 
> >> >> >> wanna.....
> >> >> >> Fedora9$> make zImge
> >> >> >> ---------------------------
> >> >> >>    ........ above omission ........
> >> >> >>   Kernel: arch/arm/boot/Image is ready
> >> >> >>   AS      arch/arm/boot/compressed/head.o
> >> >> >>   GZIP    arch/arm/boot/compressed/piggy.gz
> >> >> >>   AS      arch/arm/boot/compressed/piggy.o
> >> >> >>   CC      arch/arm/boot/compressed/misc.o
> >> >> >>   LD      arch/arm/boot/compressed/vmlinux
> >> >> >>   OBJCOPY arch/arm/boot/zImage
> >> >> >>   Kernel: arch/arm/boot/zImage is ready
> >> >> >> .............................................
> >> >> >> Feodra9$> ls -al ./arch/arm/boot/
> >> >> >> Feodra9$> cp ./arch/arm/boot/zImage /tftpboot/
>
> >> >> >> Are you ok?
> >> >> >> thank you for your bug report ...
> >> >> >> I will update notice and comment informaiton 
> >> >> >> athttp://www.kandroid.org/gitwebsite.
>
> >> >> >> I don't have free time now...
> >> >> >> i have to go out... bye...
>
> >> >> >> 2009/1/12 Praveen <praveendr...@gmail.com>:
>
> >> >> >> > Hi Lim,
>
> >> >> >> > Iam not able to build your android kernel for s3c6400 
> >> >> >> > board(samsung).
> >> >> >> > It shows the following error
>
> >> >> >> > "arch/arm/mach-s3c6400/built-in.o:(.init.data+0x1660): undefined
> >> >> >> > reference to `s3c_device_i2c'"
>
> >> >> >> > can you  provide a solution to this problem?
>
> >> >> >> > On Dec 20 2008, 12:56 pm, "Lim,GeunSik" <lee...@gmail.com> wrote:
> >> >> >> >>  Hi, Everyone...
>
> >> >> >> >>  I made git kernel tree for android platform on arm1176 core 
> >> >> >> >> basedS3C
> >> >> >> >> 64X0 board.
> >> >> >> >>  You can download kernel source file 
> >> >> >> >> athttp://www.kandroid.org/git.
> >> >> >> >>  And, If you find bug or make enhancement using this 
> >> >> >> >> S3C64X0-android-
> >> >> >> >> kernel source ,
> >> >> >> >>  Plese post athttp://www.kandroid.org/bugwebsiteorcontactto
> >> >> >> >> lee...@gmail.com.
>
> >> >> >> >>  For example,
> >> >> >> >>   1) If you want to send me patchfile like bugfix,
> >> >> >> >>      send your patch files to leemgs.at.gmail.com email.
> >> >> >> >>   2) If you want to post your opinion or bug report, connect 
> >> >> >> >> tohttp://www.kandroid.org/bug
>
> >> >> >> >>  Thank you for reading. Have nice day.
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to