Added ETH support for the cod.m WLED LAN Controller

[UtechtDustin]

Added ethernet configuration for the upcoming cod.m WLED LAN Controller.

[blazoncek]

There are no differences to the existing ESP32-POE Ethernet type. Why a new one?

  // ESP32-POE
  {
     0,                   // eth_address,
    12,                   // eth_power,
    23,                   // eth_mdc,
    18,                   // eth_mdio,
    ETH_PHY_LAN8720,      // eth_type,
    ETH_CLOCK_GPIO17_OUT  // eth_clk_mode
  },

[UtechtDustin]

If a customer of us will reset the controller it's easier to find the correct config.
Same thing like QuinLed-ESP32-Ethernet <-> TwilightLord-ESP32 Ethernet Shield.

[softhack007]

If a customer of us will reset the controller it's easier to find the correct config. Same thing like QuinLed-ESP32-Ethernet <-> TwilightLord-ESP32 Ethernet Shield.

Instead of adding a duplicate config, it's better to update the existing UI dropdown entry.
--> "ESP32-POE Ethernet or cod.m controler".

Case solved 😉

[blazoncek]

Same thing like QuinLed-ESP32-Ethernet <-> TwilightLord-ESP32 Ethernet Shield

These were added at the time when space was not yet at premium (more than 3 years ago). Unfortunately removing them is a breaking change that may render devices unreachable.

[blazoncek]

Adding a new type is only justified if it differs in HW configuration.

[UtechtDustin]

@blazoncek can we rename the option as @softhack007 suggested ?
That was also our first idea, but that could end up in something like that ESP32-POE Ethernet or cod.m controller or xyz controller or foobar ETH controller.

[blazoncek]

I'm afraid this will lead nowhere.
It will inevitably end in "Please add Adapter XXX to the list". Unfortunately I do not have an answer how should we address this issue but adding "yet another name" to the selection list is not the correct approach long term.

IMO provide a user manual where it is clearly stated that your board uses "ESP32-POE" ethernet adapter.