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: <871dab7c-3158-451f-8938-dc1ab477e725@phytec.de>
Date: Mon, 8 Jul 2024 14:31:44 +0200
From: Wadim Egorov <w.egorov@...tec.de>
To: MD Danish Anwar <danishanwar@...com>, Vignesh Raghavendra
	<vigneshr@...com>, Nishanth Menon <nm@...com>
CC: Andrew Lunn <andrew@...n.ch>, Conor Dooley <conor+dt@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Rob Herring
	<robh+dt@...nel.org>, <linux-kernel@...r.kernel.org>,
	<devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, Tero
 Kristo <kristo@...nel.org>, <srk@...com>, <r-gunasekaran@...com>, Roger
 Quadros <rogerq@...nel.org>, Daniel Schultz <D.Schultz@...tec.de>
Subject: Re: [PATCH v5 2/3] arm64: dts: ti: k3-am642-evm: add ICSSG1 Ethernet
 support

Hi,

Am 15.02.24 um 11:30 schrieb MD Danish Anwar:
> ICSSG1 provides dual Gigabit Ethernet support with proper FW loaded.
> 
> The ICSSG1 MII0 (RGMII1) has DP83869 PHY attached to it. The ICSSG1 shares
> MII1 (RGMII2) PHY DP83869 with CPSW3g and it's assigned by default to
> CPSW3g. The MDIO access to MII1 (RGMII2) PHY DP83869 is controlled by MDIO
> bus switch and also assigned to CPSW3g. Therefore the ICSSG1 MII1 (RGMII2)
> port is kept disable and ICSSG1 is enabled in single MAC mode by
> default.

sorry for bumping this old thread, but I was about to add PRU-ICSSG 
nodes for the phyBOARD-Electra and noticed a difference in the firmware 
names.

[snip]
> +	icssg1_eth: icssg1-eth {
> +		compatible = "ti,am642-icssg-prueth";
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&icssg1_rgmii1_pins_default>;
> +		sram = <&oc_sram>;
> +		ti,prus = <&pru1_0>, <&rtu1_0>, <&tx_pru1_0>, <&pru1_1>, <&rtu1_1>, <&tx_pru1_1>;
> +		firmware-name = "ti-pruss/am64x-sr2-pru0-prueth-fw.elf",
> +				"ti-pruss/am64x-sr2-rtu0-prueth-fw.elf",
> +				"ti-pruss/am64x-sr2-txpru0-prueth-fw.elf",
> +				"ti-pruss/am64x-sr2-pru1-prueth-fw.elf",
> +				"ti-pruss/am64x-sr2-rtu1-prueth-fw.elf",
> +				"ti-pruss/am64x-sr2-txpru1-prueth-fw.elf";

Where do these firmware names come from? All references I can find use 
am65x-sr2*: ti-linux-firmware, meta-ti and so on.
Are we expecting the the names to be renamed for linux-firmware?

Regards,
Wadim

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ