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]
Date: Fri, 15 Mar 2024 20:04:11 +0100
From: Dragan Simic <dsimic@...jaro.org>
To: Himanshu Bhavani <himanshu.bhavani@...iconsignals.io>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, Conor Dooley
 <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>, Lorenz Brun
 <lorenz@...n.one>, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: add &gmac2phy in rk3328-rock64

On 2024-03-15 16:02, Himanshu Bhavani wrote:
>> Unfortunately, this isn't an acceptable change to the Rock64 dts file.
>> Yes, there's the second built-in Ethernet interface in the RK3328 SoC,
>> but the Rock64 layout doesn't expose it as a separate physical network
>> interface, i.e. it isn't available as a port.
> 
> I was wondering if the Rock64 lacks a port.
> According to this link: https://pine64.org/devices/rock64/,
> it seems that there is a physical network interface available on the 
> sbc.

As I already described in my previous response, there's another Ethernet
interface in the RK3328 SoC, which the Rock64 is based on, but there's 
no
second Ethernet port on the actual printed circuit board.  That's simply
how the Rock64 was designed and manufactured.

>> Such a change would be fine to be applied to the dts by hand, by 
>> someone
>> who actually adds a second physical network port to their Rock64.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ