Hi Sandeep,
Paulraj, Sandeep wrote:
> Ben,
>
> I was taking a closer look at the DM9000 driver by trying it on the DM355
> EVM. And it behaving a little different from before, i.e before we moved to
> the NET_MULTI stuff.
>
> When the board comes after I reflash with a new U-boot image, I no lon
>
>
> Stefano,
> >
> > Paulraj, Sandeep wrote:
> > > Ben,
> > >
> > Hi,
> >
> > > When the board comes after I reflash with a new U-boot image, I no
> > > longer see the ethaddr being set. But when I do a tftp I can see the
> > > ethaddr being read. tftp complains and says no ethaddr set.
> >
>
Stefano,
>
> Paulraj, Sandeep wrote:
> > Ben,
> >
> Hi,
>
> > When the board comes after I reflash with a new U-boot image, I no
> > longer see the ethaddr being set. But when I do a tftp I can see the
> > ethaddr being read. tftp complains and says no ethaddr set.
>
> Not sure, but it seems th
Paulraj, Sandeep wrote:
> Ben,
>
Hi,
> When the board comes after I reflash with a new U-boot image, I no
> longer see the ethaddr being set. But when I do a tftp I can see the
> ethaddr being read. tftp complains and says no ethaddr set.
Not sure, but it seems that the mac address is read from
Ben,
I was taking a closer look at the DM9000 driver by trying it on the DM355 EVM.
And it behaving a little different from before, i.e before we moved to the
NET_MULTI stuff.
When the board comes after I reflash with a new U-boot image, I no longer see
the ethaddr being set. But when I do a t
5 matches
Mail list logo