The DTS would only contain an extra node for the second UART, which is connected to the PoE management MCU. Unless maybe on that TI-platform, but in any case the DTS doesn't have much info on PoE. This is all managed in userspace, so the place to specify the total power budget would be the uci config.
@RaylynnKnight I have this on my GS1900-10HP:
# cat /etc/config/poe
config poe poe
option budget 77
option port1 1
option port2 0
option port3 0
option port4 0
option port5 0
option port6 0
option port7 0
option port8 0
No PoE devices connected atm though, so nothing reported at the moment:
# ubus call poe info
{
"ports": [
"0W",
"off",
"off",
"off",
"off",
"off",
"off",
"off"
],
"power_budget": "77W",
"power_consumption": "0W"
}
I'm using the rtl83xx-poe package to manage PoE. It seems to depend on which PoE controller your board has, though (GS1900-10HP has Broadcom ones).
The power budget is preset in /etc/board.d/02_network per device:
case $board in
netgear,gs110tpp-v1)
ucidef_set_poe 130 "$lan_list"
;;
zyxel,gs1900-10hp)
ucidef_set_poe 77 "$lan_list"
;;
zyxel,gs1900-8hp-v1|\
zyxel,gs1900-8hp-v2)
ucidef_set_poe 70 "$lan_list"
;;
esac
Maybe we should make the rtl83xx-poe package a standard package of the switches which have PoE capabilities. Similarly how the network configuration for routers is set up on first boot, we could put a switch-dependent setup into /etc/board.d to define power budgets and other fundamental stuff.
2 Likes
I seem to recall @svanheule pointed out the PoE 'dialect' might depend on what PoE controller is used and the rtl83xx-poe package speaks 'Broadcom' since he was able to replicate that. But I might be mistaken. I've only had my eyes on my own ZyXEL switches when it comes to PoE chips on the boards.
That's correct, the current package only works on switches that use the BCM59111 or BCM59121 PSE controllers.
PoE switches with the Microsemi PD69xxx ICs and the TI ICs are currently not supported.
I believe I have enough information now. I am wanting to add the DGS-1210-28P and DGS-1210-28MP support, so it appears that they will share at least a dtsi with DGS-1210-28 and the 02_network configuration will be different depening on power budget. I think including the rtl83xx-poe package as standard for the PoE switches with Broadcom PoE also makes sense. I haven't had a lot of time lately, but am anticipating having some patches soon. Also will be adding the TRENDnet TPE-082WS which is essentially the same hardware as the DGS-1210-10P but with a 75W PoE budget and 256MB RAM. Should I be basing my changes on Openwrt master or on bkobi github?
3 Likes
If you want it merged in master here, on OpenWrt master. Bkobl's tree is still ahead.
The code adding OpenWrt device support would largely be unaffected by the upstreaming effort I think, the latter is a separate codebase more or less.
1 Like
Part of my confusion was that I was looking at the changes related DGS-1210-10P which doesn't currently have an entry in the /etc/board.d/02_network file. It should have an entry setting the PoE budget to 65 (i.e. ucidef_set_poe 65 "$lan_list"). Planning on submitting some patches this weekend!
There appear to be no instructions for installing on DGS-1210-10P in the commit message. I assumed it would be the same as for the DGS-1210-28 given the similarities. The DGS-1210-28 commit has the following statemtent:
To install, upload the sysupgrade image to the OEM webpage or sysupgrade
from the system running from initramfs image.
This seems to imply that the openwrt sysupgrade image can be loaded via the OEM webpage. When attempting this on the DGS-1210-10P I get the following message:
FW upgrade/backup fail, check FW file...
Has using the OEM webpage for installing OpenWrt been confirmed on the DGS-1210 series?
Thanks,
Ray
Does the Zyxel GS1900-16 qualify for this also?
As I'm eyeing the ZyXEL GS1900-24E myself, I'm interested about this question as well. The information suggests the RTL8382M SOC, shared with the already supported D-Link DGS-1210-28 rev F1, but I wonder if the 2 * RTL8218B 8-port PHY extenders would pose a complication for potentially supporting this device.
I haven't actually bought a device to play with so far[0], so I'm just curious what the chances are or if there are particular difficulties to be expected based on the known specifications (or if it would be better to look at a different device).
--
My experiences with the ZyXEL GS1900-8 have been pretty good so far.
[0] but I do have access to one GS1900-24E that's in production use.
1 Like
At least the binary OEM firmware suggests a RTL838x variant as well.
[…]/GS1900-16_Firmware_2.60(AAHJ.3)C0/_GS1900-16_Firmware_2.60(AAHJ.3)C0.bix.extracted$ strings vmlinux_org.bin | grep -i -e 838 -e linux.*mips
Linux version 2.6.19 (gcc version 3.4.4 mipssde-6.03.00-20051020) #2 PREEMPT Tue Jan 5 08:02:18 UTC 2021
RTL8380
8380_
8380_^
8380_
8380
8380_]ab
8380_
8380_
8380
8380_^
1 Like
I haven't opened mine up, but from a video it appears the Zyxel GS1900-16 has 2 identical chips inside each serving 8 ports, so is it more like 2 x 8-port switches connected via an internal port over a 1Gbps link?
Edit: the answer is no, see kobi's reply below:
These PHY chips are connected via QSGMII to the SoC, which serves 10Gbit duplex. So all external ports can talk with each other with 1GBit at the same time.
It is very likely that this device can be easily supported with just the right .dts to set up the 2 RTL8218B properly. That flashing over the web interface does not work should not be a big issue either. Normally there is some magic number wrong which codes for the right model.
1 Like
The ZyXELs can be upgraded from stock web UI in a two-step procedure. You need to create a model specific initramfs build rule with the four letter ZyXEL model code. See the examples:
Note that the current default OpenWrt network configuration is weird and will set up management on a tagged vlan 100 interface. The other end of the management link must therefore be reconfigured when changing from stock to OpenWrt.
So I recommend having console access just in case. The console header is mounted and reachable without opening the case on these ZyXEL, so all you need is the USB TTL UART adapter.
EDIT: I watched the -16 video, and it does look like the odd and unwanted child.... Looks like you have to open that one to access the console header. But at least it's mounted.
4 Likes
Thanks a lot for the info, the easily accessible serial console and the dual-firmware setup (leaving a copy of the OEM firmware in place on the second partition set of these ZyXEL devices) make them really nice to work with.
These PHY chips are connected via QSGMII to the SoC, which serves 10Gbit duplex. So all external ports can talk with each other with 1GBit at the same time.
3 Likes
Submitted a pull request to add missing PoE support to the DGS-1210-10P. If someone could review and merge I would appreciate. Will be following up with merge request for DGS-1210-10 support and DGS-1210-28P and DGS-1210-28MP after some testing. I then plan on working to add support for the TRENDnet switches I have.
1 Like
hi kobi, this is great news I have this switch XGS1210-12 also and was looking to flash the experimental firmware, would you kindly share the pre-compiled image of openwrt for non developer users looking to test the firmware?
cheers
Hi Akron,
I don't have any readily flashable images for the XGS1210-12, only development stuff with lots of debug code. I did not try flashing via the OEM web-interface for example. But you can pick up what I have:
Just use the changes to the Makefile and add the .dts for that device into a copy of the OpenWRT master code and compile. Google for compiling OpenWRT from git on how this is done: clone the OWRT code and copy over the code for the XGS into that before compiling. It should be relatively straight forward to figure out how to flash the image via the OEM web-interface (see bmork's instructions above) and if you manage, you can submit the code so that images are automatically built for everyone.
Cheers,