From: Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>
To: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"paulus@samba.org" <paulus@samba.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Backwards compatiblity for QorIQ FMAN LIODN entries
Date: Thu, 11 Apr 2019 03:28:10 +0000 [thread overview]
Message-ID: <1554953290.3747.66.camel@alliedtelesis.co.nz> (raw)
Hi Rob and Mark,
I am upgrading the kernel on a Freescale P2040 based system and have
struck an issue with LIODNs not being updated by uboot for an FMAN
ethernet port.
My system has an old uboot running which fails in its attempt to update
the fman rx port node with the required LIODN entry. This is because my
old uboot installation is looking for compatibility value "fsl,fman-
port-1g-rx" while the latest kernel defines the compatible value as
"fsl,fman-v2-port-rx" (see for
instance arch/powerpc/boot/dts/fsl/qoriq-fman-0-1g-3.dtsi).
Newer uboot looks for both values per this commit:
https://github.com/u-boot/u-boot/commit/97a8d010e029111e5711a45264a726b
edbeb24c4#diff-43243b910837283bb1d5d626f4d89d75
I am unable to update bootloaders for devices of this type in the field
so I am wondering if the correct approach is to adjust my DTS file
locally to add the compatible string my old uboot is searching for, or
if we should add this to the various qoriq-fman dtsi files in the
kernel to make this work in a nice backwards compatible way.
Let me know your opinion. I'm happy to work up a patch if you'd like to
make the change in the kernel, otherwise I'll handle it locally by
overriding the compatible string in my system's dts file.
Thanks,
Hamish M
reply other threads:[~2019-04-11 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1554953290.3747.66.camel@alliedtelesis.co.nz \
--to=hamish.martin@alliedtelesis.co.nz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox