well I don't need to have the Ethernet running for the shipped product...
but I would like to use it in production test of the next batch - so if I
can avoid an extra issue of u-boot I will
D.
> > But I'm running out of time to ship some prototypes tomorrow, and
> > this is
> > my last m
> 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
Dear "David Collier",
In message you
wrote:
> My apologies, I've posted this is AVR32_u-boot where it probably belongs.
>
> But I'm running out of time to ship some prototypes tomorrow, and this is
> my last major issue with them, so could I throw myself on the mercy of
> the assembled wisdom p
My apologies, I've posted this is AVR32_u-boot where it probably belongs.
But I'm running out of time to ship some prototypes tomorrow, and this is
my last major issue with them, so could I throw myself on the mercy of
the assembled wisdom please? Maybe someone will say - you stupid person,
you ne
4 matches
Mail list logo
