ASUS DSL-N55U(-B) support

Feature Requests
1

Hello. I found out that DSL-N55U (and DSL-N55U-B) are exactly same devices as ASUS RT-N56U, with different switch and aditional cpu+flash for DSL.

Can someone please add support to DSL-N55U and DSL-N55U-B by using RT-N56U code and changing switch configuration from RTL8367M to RTL8367R-VB?

I cross-flashed AsusWRT (original firmware) from RT-N56U to DSL-N55U-B (Annex B variant), and everything excepting etherenet ports (because different swtich) was working exactly as expected from RT-N56U. DSL wasnt working ofc, but it is expected.

Then i flashed openwrt, and soft-bricked device, as openwrt doesnt ship with pre-enabled wifi. But im about to configure it using UART.

So, by using RT-N56U with RTL8367R-VB switch support, we can get DSL-N55U support without DSL. But still better than nothing.

Thank you.

EDIT: using UART i was able to access OpenWRT. Both radios are visible. I set up Wifi AP on both radios, and now i can access luci. Everything excepting ethernet ports (and dsl ofc) is working on openwrt image built for RT-N56U. Also got it working as AccessPoint with USB Ethernet adapter, but i have only 100mbps adapter.

2

In other words, they are not exactly the same hardware, but differ and need their own bespoke firmware images.

That 'someone' can only be someone who actually has the device on their desk, opened up, attached to a serial console and does the necessary development - you might be that someone, but you're relatively unlikely to find someone else doing it for you (especially for the hardware you're talking about, there is better, cheaper and much easier stuff out there).

This is a bad first step, as the resulting Frankenstein makes it basically impossible for you (or hypothetical 'others' potentially wanting to assist you) to confirm anything about the device - and you might have already irretrievably overwritten crucial data (calibration data, device specific info) and damaged the original partitioning (which would need to form the basis for any kind of official OpenWrt support).

So you've effectively made your path harder, if not impossible, without retaining a functional (representative for the stock-) device.