In message <019401c3bf34$fcbcc4a0$1b72fea9@xxxxxxxxx>
"Ulf Samuelsson" <ulf@xxxxxxxxx> wrote:
> > Most people won't notice this, because they'll be booting from tftp.
> > However, in this instance, I have a ramdisk and kernel in flash. If
> > u-boot doesn't prod the ethernet (e.g. by tftping a random file), then
> > it turns out that the ethernet doesn't work from within Linux. I'm
> > afraid I'm not able to shed any further light on why it doesn't, but
> > perhaps someone else can.
> >
>
> Did you set the "ethaddr" in u-boot properly? If you managed to ftp, I guess
> it should work.
I don't think you read what I wrote correctly. The point is that I'm
_not_ using tftp. There is no ethernet activity from u-boot.
In any case, I have put a work around of putting a call to eth_init()
near the end of the ARM specific initialisation, which does the right
thing. I will talk to the u-boot people in more detail about what a
correct fix would be. For any one who cares, the latest CVS version of
u-boot for this board is also broken in the last week or so.
--
Peter Naulls - peter@xxxxxxxxxx | http://www.chocky.org/
----------------------------------------------------------------------------
The RISC OS Browser Issue - http://www.chocky.org/unix/browser.html
-------------------------------------------------------------------
Subscription options: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ/Etiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php
|
