[ELDK] eldk testing
Detlev Zundel
dzu at denx.de
Fri Jan 11 01:36:42 CET 2008
Hi Derek,
> I've been trying out the new version of the ELDK on an MPC8540
> processor and have found a few things. I build the kernel
> successfully using the mpc8540_ads_defconfig default config file in
> the arch/ppc/configs folder. When this kernel starts up, there is a
> large pause (1 - 2 minutes) after the text "Starting system logger:".
> After a couple of minutes the OK text appears and it carries on as
> normal.
Hm, yes, we have seen such a phenomenon. It was triggered by the fact
that the arch/ppc kernel erroneously tried to use vdso support not
supported in arch/ppc to handle gettimeofday. The fix should be this
commit
commit dc9b43d0f706852fc4abce5bf28958db41524328
Author: Wolfgang Denk <wd at denx.de>
Date: Wed Oct 10 08:36:18 2007 +1000
[POWERPC] Disable vDSO support for ARCH=ppc where it's not
implemented
Signed-off-by: Wolfgang Denk <wd at denx.de>
Signed-off-by: Paul Mackerras <paulus at samba.org>
I'll check later why this is not in the ELDK linux tree.
> I tried building u-boot using the following:
>
> make distclean
> make MPC8540ADS_config
> make
>
> The build fails on the besys.c file.
That should not happen and I don't think its a known problem. I have to
check later what may cause this.
> I also tried using the uRamdisk file that is part of the SELF rpm.
> When the kernel tries to use this it goes into a panic.
> The error says there is no init file.
This should also not happen - could you please post a complete log of
the boot procedure including the U-Boot statements to start the kernel?
Thanks
Detlev
--
Alisa Sherer (AMD) suggested that consumer demand will not follow
faster clock speeds. Marketing might help with this problem, she
added. -- 2004/02/20
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
More information about the eldk
mailing list