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
| ||
|
Message-ID: <CAOMZO5ANFe1AH2PqafbHd97G0L=-LnSyHt5VjBKh0EAskm5JBw@mail.gmail.com> Date: Thu, 27 Oct 2022 23:24:40 -0300 From: Fabio Estevam <festevam@...il.com> To: Vladimir Oltean <vladimir.oltean@....com> Cc: Andrew Lunn <andrew@...n.ch>, "tharvey@...eworks.com" <tharvey@...eworks.com>, netdev <netdev@...r.kernel.org>, Marek Vasut <marex@...x.de>, Fabio Estevam <festevam@...x.de> Subject: Re: Marvell 88E6320 connected to i.MX8MN Hi Vladimir, On Thu, Oct 27, 2022 at 5:41 PM Vladimir Oltean <vladimir.oltean@....com> wrote: > Looks like you are missing the Marvell PHY driver; the generic PHY > driver gets used. Can you enable CONFIG_MARVELL_PHY? CONFIG_MARVELL_PHY is already selected. However, there is no support for 88E6320 in the Marvell PHY driver. Thanks > > device eth0 entered promiscuous mode > > DSA: tree 0 setup > > ... > > > > ~# udhcpc -i lan4 > > udhcpc: started, v1.31.1 > > [ 25.174846] mv88e6085 30be0000.ethernet-1:00 lan4: configuring for > > phy/gmii link mode > > udhcpc: sending discover > > [ 27.242123] mv88e6085 30be0000.ethernet-1:00 lan4: Link is Up - > > 100Mbps/Full - flow control rx/tx > > [ 27.251064] IPv6: ADDRCONF(NETDEV_CHANGE): lan4: link becomes ready > > udhcpc: sending discover > > udhcpc: sending discover > > udhcpc: sending discover > > ... > > > > This is my devicetree: > > https://pastebin.com/raw/TagQJK2a > > > > The only way that I can get IP via DHCP to work in the kernel is if > > I access the network inside U-Boot first and launch the kernel afterward. > > > > It looks like U-Boot is doing some configuration that the kernel is missing. > > Yeah, sounds like the Marvell PHY driver could be what's the difference. > > > Does anyone have any suggestions, please? > > If that doesn't work, the next step is to isolate things. Connect a > cable to the other switch port, create a bridge, and forward packets > between one station and the other. This doesn't involve the CPU port, so > you'll learn if the internal PHYs are the problem or the CPU port is. > Next step would be to collect ethtool -S lan0, ethtool -S eth0, and post > those.
Powered by blists - more mailing lists