[U-Boot] u-boot-v2 2.0.0 rc7 broken compatibility with SMSC LAN9313 vs rc3

For u-boot-v2 from: git clone git://www.denx.de/git/u-boot-v2.git 2.0.0 rc3 ran both the SMSC8700 and the idealized IEEE MII Virtual Phy of the SMSC9313 from the i.mx27 using /arch/arm and /board ads27 or pcm038. (or any other board built on pattern.) 2.0.0 rc7 no longer supports the SMSC9313

[U-Boot] u-boot-v2 compatibility broken with Spansion S29GL512/256/128N in rc7

For u-boot-v2 from: git clone git://www.denx.de/git/u-boot-v2.git 2.0.0 rc3 ran all ST and Spansion CFI NOR flash from the i.mx27 using /arch/arm and /board ads27 or pcm038. (or any other board built on pattern.) 2.0.0 rc7 no longer supports the SPANSION S29GL512/256/128N programing ST is

[U-Boot] test please ignore

test please ignore ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] 2.0.0 RC7 MACH_TYPE_*NEW*

For 2.0.0-rc7-00037-ge983361-dirty (a fresh git pull) one has to register a MACH_TYPE_??? for a new board with a number. This appears to have been extracted from the Linux kernel traditionally. Who is handing these out for u-boot-v2? The arm maintainer (I seriously think it is but am

[U-Boot] u-boot-v2 rc7

In ~/u-boot-v2/board/pcm038/env/config (and in most other boards in v2) the following is found: /+ autoboot_timeout=3 nfsroot=/ptx/work/octopus/rsc/svn/oselas/bsp/phytec/phyCORE-i.MX27/OSELAS.BSP-Phytec-phyCORE-i.MX27-trunk/root bootargs=console=ttymxc0,115200 -/ I believe this causes

[U-Boot] u-boot-v2

Hi If I use for u-boot-v2 #ln -s arm cross_arch #ln -s /opt/arm-v5te-linux-gnueabi/gcc-4.1.2-glibc-2.5-binutils-2.17-kernel-2.6.18/arm-v5te-linux-gnueabi/bin \ cross_compile During make menuconfig the arm is not picked up as the architecture. I appear to get sandbox. Obviously I am not