From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: frank-w@public-files.de, Daniel Golle <daniel@makrotopia.org>
Cc: Frank Wunderlich <linux@fw-web.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: mediatek: mt7988a-bpi-r4: allow hw variants of bpi-r4
Date: Tue, 15 Apr 2025 11:56:37 +0200 [thread overview]
Message-ID: <8fe762e3-a9eb-4a9c-81a2-b7a10539b615@collabora.com> (raw)
In-Reply-To: <D7682B25-5BEF-46D1-A5FD-32D2AAF84EFF@public-files.de>
Il 15/04/25 10:07, Frank Wunderlich ha scritto:
> Am 15. April 2025 09:36:43 MESZ schrieb AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>:
>> Il 14/04/25 14:32, Daniel Golle ha scritto:
>>> On Mon, Apr 14, 2025 at 11:27:23AM +0200, AngeloGioacchino Del Regno wrote:
>>>> Il 12/04/25 12:21, Frank Wunderlich ha scritto:
>>>>> From: Frank Wunderlich <frank-w@public-files.de>
>>>>>
>>>>> Sinovoip has released other variants of Bananapi-R4 board.
>>>>> The known changes affecting only the LAN SFP+ slot which is replaced
>>>>> by a 2.5G phy with optional PoE.
>>>>>
>>>>> Just move the common parts to a new dtsi and keep differences (only
>>>>> i2c for lan-sfp) in dts.
>
>>>> This should at least have some different compatible, if not probably also a
>>>> different model string - as it's a different device.
>>>>
>>>> compatible = "bananapi,bpi-r4-2g5", "bananapi,bpi-r4", "mediatek,mt7988a";
>>>
>>> Imho it doesn't make sense to declare compatibility with the
>>> "bananapi,bpi-r4" as the "bananapi,bpi-r4-2g5" is NOT compatible with the
>>> "bananapi,bpi-r4". It's a different board and using firmware meant for the
>>> "bananapi,bpi-r4-2g5" on the "bananapi,bpi-r4" (or vice versa) will result
>>> in a non-working Ethernet port.
>>>
>>
>> Is this device a BananaPi R4 variant, or is it a completely different device?
>
> The only difference is that sfp-lan is replaced by RJ45 socket with mt7988 internal phy.
>
Perfect, then:
- The only difference is one routing
- The base board is the same
- Same hw project
- The two machines are compatible with each other
...bar one difference
...then the compatibles shall be as I said before :-)
>> If this is a completely different device, then it's not even a BananaPi R4,
>> otherwise this is compatible with BananaPi R4, with a small variation :-)
>
> Sinovoip now announces a R4Pro with some more changes (e.g. an external 2.5g switch),but we have no detailed shematic yet. It looks they also plan a R4lite which is based on different SoC (afair mt7987),but this is for sure different device (and so not using this bpi-r4.dtsi).
In that case, R4Lite shall not be compatible with R4, as the name may be the
same, but in practice it's a different machine.
>
> But basicly all are named BPi-R4. I guess R4Pro will also get own dts as too much changed.
If R4pro is a redesign of the R4 board, that would not be compatible, as it
would not be the same base design; otherwise, I'm sure you have well understood
how it works for the compatibles, anyway :D
Cheers!
>
>> Cheers,
>> Angelo
>
>
> regards Frank
next prev parent reply other threads:[~2025-04-15 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 10:21 Frank Wunderlich
2025-04-14 9:27 ` AngeloGioacchino Del Regno
2025-04-14 10:19 ` Frank Wunderlich
2025-04-14 11:20 ` AngeloGioacchino Del Regno
2025-04-14 12:32 ` Daniel Golle
2025-04-15 7:36 ` AngeloGioacchino Del Regno
2025-04-15 8:07 ` Frank Wunderlich
2025-04-15 9:56 ` AngeloGioacchino Del Regno [this message]
2025-04-15 10:30 ` Frank Wunderlich
2025-04-15 10:57 ` AngeloGioacchino Del Regno
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=8fe762e3-a9eb-4a9c-81a2-b7a10539b615@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®