Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Apr 2016 12:28:52 +0300
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        =?utf-8?Q?=22Wei=C3=9F=2C_Dr=2E_J=C3=BCrgen=22?= <weiss@uni-mainz.de>
Cc:        freebsd-arm <freeBSD-arm@freebsd.org>
Subject:   Re: Odroidc1+ ethernet(dwc0) not working
Message-ID:  <9C393F68-3355-48B0-A21D-00208407D5D0@cs.huji.ac.il>
In-Reply-To: <da68a99a7c924cee8d3dd78e7dbc3170@uni-mainz.de>
References:  <A0F7E1EB-3208-4DEB-8E3E-538E2D92296D@cs.huji.ac.il> <773D8BC8-EA89-42AA-A251-9DE37F7B9750@cs.huji.ac.il> <da68a99a7c924cee8d3dd78e7dbc3170@uni-mainz.de>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 17 Apr 2016, at 18:20, Wei=C3=9F, Dr. J=C3=BCrgen =
<weiss@uni-mainz.de> wrote:
>=20
> 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.
>=20
not nice.
this is what I see:
...
dwc0: <Amlogic Meson Gigabit Ethernet Controller> mem =
0xc9410000-0xc9411fff irq 10017 on simplebus0
miibus0: <MII bus> on dwc0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on =
miibus0
rgephy0: OUI 0x00e04c, model 0x0011, rev. 6
000baseT-FDX-master, auto
random: harvesting attach, 8 bytes (4 bits) from rgephy0
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on =
miibus0
rgephy1: OUI 0x00e04c, model 0x0011, rev. 6
000baseT-FDX-master, auto
random: harvesting attach, 8 bytes (4 bits) from rgephy1
random: harvesting attach, 8 bytes (4 bits) from miibus0
dwc0: bpf attached
dwc0: Ethernet address: 62:73:64:b7:54:2e
..

also, I think that the fact that kenv(1) does not show anything
means there is something else fishy.

danny

> Actually, this comment is from the driver:
>=20
>         * 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.
>         */
>=20
> Regards
>=20
> Juergen=20
>=20
>=20
>> -----Original Message-----
>> From: owner-freebsd-arm@freebsd.org =
[mailto:owner-freebsd-arm@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
>>=20
>>=20
>>> On 15 Apr 2016, at 10:29 AM, Daniel Braniss <danny@cs.huji.ac.il> =
wrote:
>>>=20
>>> 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 ...
>>=20
>> very strange,
>> 1- doing a netboot (bootp the go =E2=80=A6) 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)
>>=20
>> go figure,
>>=20
>> 	danny
>>=20
>> _______________________________________________
>> freebsd-arm@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to =
"freebsd-arm-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9C393F68-3355-48B0-A21D-00208407D5D0>