Odroidc1+ ethernet(dwc0) not working

Weiß, Dr. Jürgen weiss at uni-mainz.de
Sun Apr 17 15:20:39 UTC 2016


It seems the FreeBSD driver is only able to use the
mac address which is already programmed into the nic.
So if you use a command in u-boot, which needs and
initializes the network, FreeBSD uses the same mac
address as u-boot. If not it seems to be random.

Actually, this comment is from the driver:

         * Try to recover a MAC address from the running hardware. If there's
         * something non-zero there, assume the bootloader did the right thing
         * and just use it.
         *
         * Otherwise, set the address to a convenient locally assigned address,
         * 'bsd' + random 24 low-order bits.  'b' is 0x62, which has the locally
         * assigned bit set, and the broadcast/multicast bit clear.
         */

Regards

Juergen 


> -----Original Message-----
> From: owner-freebsd-arm at freebsd.org [mailto:owner-freebsd-arm at freebsd.org] On Behalf Of
> Daniel Braniss
> Sent: Saturday, April 16, 2016 4:40 PM
> To: freebsd-arm
> Subject: Re: Odroidc1+ ethernet(dwc0) not working
> 
> 
> > On 15 Apr 2016, at 10:29 AM, Daniel Braniss <danny at cs.huji.ac.il> wrote:
> >
> > Hi,
> > after cleaning my act, I now have a working current, but
> > the dwc ethernet is not. I can netboot, so the hardware/link is ok,
> > any hints? BTW, kenv is also empty ...
> 
> very strange,
> 1- doing a netboot (bootp the go …) loads the kernel, starts up but the dwc, is
>      not working
> 2- booting from the sd ,the dwc works, but has a different mac (ethernet address)
> 
> go figure,
> 
> 	danny
> 
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"


More information about the freebsd-arm mailing list