Message ID | 1414630580-24640-2-git-send-email-isubramanian@apm.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Wednesday 29 October 2014 17:56:19 Iyappan Subramanian wrote: > @@ -621,7 +621,7 @@ > }; > }; > > - sgenet0: ethernet@1f210000 { > + sgenet0: sgenet@1f210000 { > compatible = "apm,xgene-enet"; > status = "disabled"; > reg = <0x0 0x1f210000 0x0 0x10000>, > This looks like you accidentally reverted a bug fix made earlier. Network devices should always have the name 'ethernet@...'. Arnd
Hi Arnd, On Thu, Oct 30, 2014 at 3:13 AM, Arnd Bergmann <arnd@arndb.de> wrote: > On Wednesday 29 October 2014 17:56:19 Iyappan Subramanian wrote: >> @@ -621,7 +621,7 @@ >> }; >> }; >> >> - sgenet0: ethernet@1f210000 { >> + sgenet0: sgenet@1f210000 { >> compatible = "apm,xgene-enet"; >> status = "disabled"; >> reg = <0x0 0x1f210000 0x0 0x10000>, >> > > This looks like you accidentally reverted a bug fix made earlier. > Network devices should always have the name 'ethernet@...'. Thanks for the review. Since our firmware was patching the dtb, based on the node-name, we thought by changing node-name, we can avoid the patching and maintain backward compatibility. Now we know that network devices should have 'ethernet@...', we will handle the backward compatibility in a different way and will post the patch v2 shortly. > > Arnd
On Monday 03 November 2014 11:45:44 Iyappan Subramanian wrote: > > On Thu, Oct 30, 2014 at 3:13 AM, Arnd Bergmann <arnd@arndb.de> wrote: > > On Wednesday 29 October 2014 17:56:19 Iyappan Subramanian wrote: > >> @@ -621,7 +621,7 @@ > >> }; > >> }; > >> > >> - sgenet0: ethernet@1f210000 { > >> + sgenet0: sgenet@1f210000 { > >> compatible = "apm,xgene-enet"; > >> status = "disabled"; > >> reg = <0x0 0x1f210000 0x0 0x10000>, > >> > > > > This looks like you accidentally reverted a bug fix made earlier. > > Network devices should always have the name 'ethernet@...'. > > Thanks for the review. Since our firmware was patching the dtb, based > on the node-name, we thought by changing node-name, we can avoid the > patching and maintain backward compatibility. > > Now we know that network devices should have 'ethernet@...', we will > handle the backward compatibility in a different way and will post the > patch v2 shortly. It's not important enough to break backwards compatibility over this. If you can't find a better way to handle compatibility with the old firmware, just add a comment explaining the node name. Arnd
diff --git a/arch/arm64/boot/dts/apm-mustang.dts b/arch/arm64/boot/dts/apm-mustang.dts index 2e25de0..f649000 100644 --- a/arch/arm64/boot/dts/apm-mustang.dts +++ b/arch/arm64/boot/dts/apm-mustang.dts @@ -40,11 +40,3 @@ &menet { status = "ok"; }; - -&sgenet0 { - status = "ok"; -}; - -&xgenet { - status = "ok"; -}; diff --git a/arch/arm64/boot/dts/apm-storm.dtsi b/arch/arm64/boot/dts/apm-storm.dtsi index 295c72d..52488c8 100644 --- a/arch/arm64/boot/dts/apm-storm.dtsi +++ b/arch/arm64/boot/dts/apm-storm.dtsi @@ -621,7 +621,7 @@ }; }; - sgenet0: ethernet@1f210000 { + sgenet0: sgenet@1f210000 { compatible = "apm,xgene-enet"; status = "disabled"; reg = <0x0 0x1f210000 0x0 0x10000>, @@ -635,7 +635,7 @@ phy-connection-type = "sgmii"; }; - xgenet: ethernet@1f610000 { + xgenet: xgenet@1f610000 { compatible = "apm,xgene-enet"; status = "disabled"; reg = <0x0 0x1f610000 0x0 0xd100>,