From: Gabor Juhos <j4g8y7@gmail.com>
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Linus Walleij <linusw@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Yury Norov" <yury.norov@gmail.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Russell King" <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 06/10] net: dsa: realtek: rtl8365mb: add VLAN support
Date: Tue, 28 Apr 2026 11:26:08 +0200 [thread overview]
Message-ID: <232d7c53-f413-4c8d-bc70-f03a12d601f5@gmail.com> (raw)
In-Reply-To: <CAJq09z6PjXeDYhfo3=UmLyUhXyx5rPHCK4kBaMaJWNZNssjo2Q@mail.gmail.com>
Hi Luiz, Linus,
Sorry for the late reply.
>
>>> I haven't yet wrapped my head around if the RTL8367 (no extra letters)
>>> is more RTL8366RB-ish or more RTL8365MB-ish... take a look at the
>>> old code if you can figure it out from register maps etc:
>>> https://github.com/openwrt/openwrt/tree/main/target/linux/generic/files/drivers/net/phy
>>> (maybe Gabor knows, put him on cc)
>
> Regarding the RTL8367 (no extra letters), the RTL8367R is indeed a
> member of that original family, rather than the "B" family as I
> previously suggested. It uses Port 9 for the CPU, which is absent in
> RTL8367B. Architecturally, it is definitely more RTL8365MB-ish.
I wrote the rtl8367 driver for the RTL8367R and RTL8367M switches. I have
no datasheet for those chips, but there are some basic information about
their features [1].
The driver was based on various code found in GPL sources of the TP-Link
TL-WR2543ND and ASUS RT-N56U devices. Those sources were using the RTL8370
specific API for these chips.
It was not clear that the two models really belongs to the RTL8370 family
or simply the vendors were using the RTL8370 specific code as a base, so
I have used RTL8367 prefix in the swconfig driver. Probably, it would have
been better to keep the RTL8370 prefix to avoid confusion.
>
> The main challenge with the base RTL8367 is the lack of a public API.
> Most vendors support it via binary managers (ASUS) or proprietary
> kernel modules (TP-Link). The only available references I’ve found are
> the OpenWrt swconfig driver you mentioned and some U-Boot
> initialization code. I do have the rtl8367{b,c,d} APIs. While the
> rtl8367b seems close to the original RTL8367, it has fewer ports. Does
> anyone happen to have access to the original RTL8367 API
> documentation?
I have no documentation, but the RTL8370 API source can be found at various
places [2], [3].
To be honest, I don't remember all the details, but I hope that this helps.
Regards,
Gabor
[1] http://semitron.co.kr/product/product.php?lcate=001&mcate=005&scate=004&uid=47&PHPSESSID=ec195486d91ed175f698567462571180
[2] https://github.com/cgoder/openwrt_rtk/tree/master/rtk_openwrt_sdk/target/linux/rtkmipsel/files/drivers/net/rtl819x/RTL8370_RTL8367_API
[3] https://github.com/andy-padavan/rt-n56u/tree/master/uboot/mips/uboot-5.x.x.x/drivers/rtl8367/api_8370
next prev parent reply other threads:[~2026-04-28 9:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 23:00 [net-next PATCH 00/10] net: dsa: realtek: rtl8365mb: bridge offloading and VLAN support Luiz Angelo Daros de Luca
2026-03-31 23:00 ` [net-next PATCH 01/10] net: dsa: tag_rtl8_4: update format description Luiz Angelo Daros de Luca
2026-04-07 7:33 ` Linus Walleij
2026-03-31 23:00 ` [net-next PATCH 02/10] net: dsa: realtek: rtl8365mb: set STP state to disabled early Luiz Angelo Daros de Luca
2026-03-31 23:00 ` [net-next PATCH 03/10] net: dsa: realtek: rtl8365mb: prepare for multiple source files Luiz Angelo Daros de Luca
2026-04-07 7:35 ` Linus Walleij
2026-03-31 23:00 ` [net-next PATCH 04/10] bitfield.h: add FIELD_WIDTH() Luiz Angelo Daros de Luca
2026-04-01 2:15 ` Yury Norov
2026-04-02 4:00 ` Luiz Angelo Daros de Luca
2026-04-02 9:27 ` David Laight
2026-04-02 13:52 ` Yury Norov
2026-04-02 22:21 ` David Laight
2026-04-03 14:09 ` Luiz Angelo Daros de Luca
2026-04-03 16:18 ` Yury Norov
2026-04-04 14:54 ` David Laight
2026-04-04 15:12 ` David Laight
2026-04-02 13:45 ` Yury Norov
2026-03-31 23:00 ` [net-next PATCH 05/10] net: dsa: realtek: rtl8365mb: add table lookup interface Luiz Angelo Daros de Luca
2026-04-07 7:43 ` Linus Walleij
2026-03-31 23:00 ` [net-next PATCH 06/10] net: dsa: realtek: rtl8365mb: add VLAN support Luiz Angelo Daros de Luca
2026-04-01 2:27 ` Yury Norov
2026-04-02 2:45 ` Luiz Angelo Daros de Luca
2026-04-02 14:22 ` Yury Norov
2026-04-07 7:59 ` Linus Walleij
2026-04-10 7:05 ` Luiz Angelo Daros de Luca
2026-04-10 7:36 ` Linus Walleij
2026-04-22 4:10 ` Luiz Angelo Daros de Luca
2026-04-27 18:07 ` Luiz Angelo Daros de Luca
2026-04-27 20:11 ` Linus Walleij
2026-04-28 9:26 ` Gabor Juhos [this message]
2026-03-31 23:00 ` [net-next PATCH 07/10] net: dsa: realtek: rtl8365mb: add port_bridge_{join,leave} Luiz Angelo Daros de Luca
2026-04-07 8:11 ` Linus Walleij
2026-04-22 5:42 ` Luiz Angelo Daros de Luca
2026-03-31 23:00 ` [net-next PATCH 08/10] net: dsa: realtek: rtl8365mb: add FDB support Luiz Angelo Daros de Luca
2026-04-07 9:11 ` Linus Walleij
2026-04-22 6:56 ` Luiz Angelo Daros de Luca
2026-03-31 23:00 ` [net-next PATCH 09/10] net: dsa: realtek: rtl8365mb: add bridge port flags Luiz Angelo Daros de Luca
2026-04-07 9:20 ` Linus Walleij
2026-04-22 6:06 ` Luiz Angelo Daros de Luca
2026-03-31 23:00 ` [net-next PATCH 10/10] net: dsa: tag_rtl8_4: set KEEP flag Luiz Angelo Daros de Luca
2026-04-07 9:22 ` Linus Walleij
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=232d7c53-f413-4c8d-bc70-f03a12d601f5@gmail.com \
--to=j4g8y7@gmail.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=yury.norov@gmail.com \
/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