Interesting sight to see Realtek device with a relatively "recent" kernel of Linux version 5.10.70. They are usually based on very old like 2.x or 3.x.
RAM and Flash size seems to be on a good end but adding a support is a tough order because its Realtek.
# ls /sys/firmware/fdt -l
-r-------- 1 root root 4343 Jan 1 09:09 /sys/firmware/fdt
ku@debian:~$ dtc -I dtb ./fdt > fdt.dts
<stdout>: Warning (reg_format): /ethernet@0/gmac0:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
<stdout>: Warning (reg_format): /ethernet@0/gmac1:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
<stdout>: Warning (reg_format): /ethernet@0/gmac2:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
<stdout>: Warning (unit_address_vs_reg): /cpuintc@0: node has a unit name, but no reg or ranges property
<stdout>: Warning (unit_address_vs_reg): /switch@0: node has a unit name, but no reg or ranges property
<stdout>: Warning (unit_address_vs_reg): /ethernet@0: node has a unit name, but no reg or ranges property
<stdout>: Warning (unit_address_vs_reg): /ethernet@0/gmac0: node has a reg or ranges property, but no unit name
<stdout>: Warning (unit_address_vs_reg): /ethernet@0/gmac1: node has a reg or ranges property, but no unit name
<stdout>: Warning (unit_address_vs_reg): /ethernet@0/gmac2: node has a reg or ranges property, but no unit name
<stdout>: Warning (unit_address_vs_reg): /usb@0: node has a unit name, but no reg or ranges property
<stdout>: Warning (unit_address_vs_reg): /usb@1: node has a unit name, but no reg or ranges property
<stdout>: Warning (unit_address_vs_reg): /usb@2: node has a unit name, but no reg or ranges property
<stdout>: Warning (pci_device_reg): Failed prerequisite 'reg_format'
<stdout>: Warning (pci_device_bus_num): Failed prerequisite 'reg_format'
<stdout>: Warning (simple_bus_reg): Failed prerequisite 'reg_format'
<stdout>: Warning (i2c_bus_reg): Failed prerequisite 'reg_format'
<stdout>: Warning (spi_bus_reg): Failed prerequisite 'reg_format'
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac0: Relying on default #address-cells value
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac0: Relying on default #size-cells value
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac1: Relying on default #address-cells value
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac1: Relying on default #size-cells value
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac2: Relying on default #address-cells value
<stdout>: Warning (avoid_default_addr_size): /ethernet@0/gmac2: Relying on default #size-cells value
<stdout>: Warning (avoid_unnecessary_addr_size): Failed prerequisite 'avoid_default_addr_size'
<stdout>: Warning (unique_unit_address): Failed prerequisite 'avoid_default_addr_size'
<stdout>: Warning (interrupt_provider): /ictl@1f000000: Missing #address-cells in interrupt provider
<stdout>: Warning (interrupt_provider): /gic@1fbc0000: Missing #address-cells in interrupt provider
<stdout>: Warning (interrupt_provider): /gpio-controller@1b000038/bank@0: Missing #address-cells in interrupt provider
<stdout>: Warning (interrupt_provider): /gpio-controller@1b000038/bank@1: Missing #address-cells in interrupt provider
<stdout>: Warning (interrupt_provider): /gpio-controller@1b000038/bank@2: Missing #address-cells in interrupt provider
I could extract kallsyms from /proc/kallsyms. This helps me to invest kernel functions (and associated hardware registers) with analysis tools like Ghidra.