netdev - RE: Fw: [Bug 205215] New: Amiga X5000 Cyrus board DPAA network driver issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <VI1PR04MB55677FB8BC9504E429ED86D2EC6C0@VI1PR04MB5567.eurprd04.prod.outlook.com>
Date:   Fri, 18 Oct 2019 11:40:36 +0000
From:   Madalin-cristian Bucur <madalin.bucur@....com>
To:     Maxim Uvarov <muvarov@...il.com>,
        Stephen Hemminger <stephen@...workplumber.org>
CC:     netdev <netdev@...r.kernel.org>
Subject: RE: Fw: [Bug 205215] New: Amiga X5000 Cyrus board DPAA network driver
 issue

> -----Original Message-----
> From: Maxim Uvarov <muvarov@...il.com>
> Sent: Friday, October 18, 2019 11:42 AM
> To: Stephen Hemminger <stephen@...workplumber.org>
> Cc: Madalin-cristian Bucur <madalin.bucur@....com>; netdev
> <netdev@...r.kernel.org>
> Subject: Re: Fw: [Bug 205215] New: Amiga X5000 Cyrus board DPAA network
> driver issue
> 
> чт, 17 окт. 2019 г. в 20:27, Stephen Hemminger
> <stephen@...workplumber.org>:
<snip>
> > So what is happening,
> >
> > First of all the hardware is functional. When using AmigaOS4.1FE the
> Ethernet
> > adapter is fine. When using the adapter within U-boot (ping for example)
> it is
> > also working as expected.
> >
> > When booted into linux the ethernet adapter does not get up.
> > The output of DMESG is:
> >
> > skateman@...00LNX:~$ dmesg | grep eth
> > [ 4.740603] fsl_dpaa_mac ffe4e6000.ethernet: FMan dTSEC version:
> 0x08240101
> > [ 4.741026] fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address:
> > 00:04:a3:6b:41:7c
> > [ 4.741387] fsl_dpaa_mac ffe4e8000.ethernet: FMan dTSEC version:
> 0x08240101
> > [ 4.741740] fsl_dpaa_mac ffe4e8000.ethernet: FMan MAC address:
> > 00:1e:c0:f8:31:b5
> > [ 4.742001] fsl_dpaa_mac ffe4e0000.ethernet:
> > of_get_mac_address(/soc@...000000/fman@...000/ethernet@...00) failed
> 
> sound like mac is missing in dt.
> 

Indeed, if you do not set the required u-boot env entries, the MAC address
fixup of the device tree will not be performed and the driver will not 
probe those MACs. The question is - are the interfaces that do probe
functional?

Madalin