This is unlogical. Instead of updating and fixing "the saveenv issue" (whatever this is) you are using old code - where you now have to fix "the PHY issue".
the saveenv issue was that when I tried to work with the latest sources for the AVR32 it wouldn't do savenv.
So I backed off to the last commit which did it OK, which was 2008.10.
Is this any better?
well yes, in that I don't HAVE to fix this now, I just want to, and I have no experience in producing diff patches, and getting them included.
I really need to go through the whole business of defining a new board, but I don't have the time for tomorrow's timescale.
SOmetimes pragmatism is required.
David
...
the linux startup says:
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:10, irq=-1) eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1)
now we have strapped PHYAD4 high, so the 2 phys should have addresses binary 10000 and 10001
I can't see any relationship between 0:10 and 1:00 and 10000 and 10001 !!!
...
well maybe - the first one looks right - binary 10000 is hex 10 but the other port should be on hex 11, not hex 0!!!!!!
Maybe your haredware is not what you think it is?
but under u-boot
in my file derived from ATNGW10.c I have
void board_init_info(void) { gd->bd->bi_phy_id[0] = 0x01; gd->bd->bi_phy_id[1] = 0x03; }
I can't see any relationship between 0x01 and 0x03 and 10000 and 10001 (or 0:10 and 1:00 either). Maybe you try these instead?
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Even if you can deceive people about a product through misleading statements, sooner or later the product will speak for itself.
- Hajime Karatsu
David Collier
www.dexdyne.com