[OpenWrt-Devel] ramips: adding support for TRENDnet DIR-810DR

[Heppler, J. Scott]

The prior post had a question on the default MAC address.  My build
generates the Trendnet portion of the MAC but not the model.  This is
the behavior of the D-Link DIR-810L code.  As I'm new to the build
system and was basing my build on the DIR-810L, do I need to do more?

On Mar 09, 2020: 13:28, Adrian Schmutzler wrote:
>Hi,
>
>> -----Original Message-----
>> From: openwrt-devel [mailto:openwrt-devel-bounces at lists.openwrt.org] On
>> Behalf Of Heppler, J. Scott
>> Sent: Samstag, 7. März 2020 22:24
>> To: openwrt-devel at openwrt.org
>> Subject: [OpenWrt-Devel] ramips: adding support for TRENDnet DIR-810DR
>>
>> I'm looking for some clarification on a prior patch:
>>
>> I'm generating a new snapshot build and have the following questions:
>>
>> 1)  My prior patch was criticized for a lack of
>> mt7620/base-files/etc/board.d/01_leds entry.  I was basing my build on
>> the D-Link DIR-810L which seems to have the same Cameo manufactured
>> board.  The D-Link lacks any entries in 01_leds.  Is this an oversight
>> that I, and DIR-810L entry will need to correct?  Or is it just not
>> needed?
>
>I was not aware that the WAN LED seems to be controlled by the driver and not by the device-tree or userspace code (as reported by Roger).
>
>If that's also the case for your device, you won't need to enter anything into 01_leds.
>
>How's the WAN LED behaving for you and is it referring to the correct port (or a wrong one as Roger reported for DIR-810L).

The Globe Lens which contains green and orange(amber) leds is
non-functional on the TEW-810DR. I have a TEW-732BR with this entry:
tew-732br)
ucidef_set_led_netdev "wan" "WAN" "trendnet:green:wan" "eth1"

This makes me think there is a missing LED entry in the DIR-810L dts.
Physically, both the DIR-810L, TEW-732BR and TEW-810DR have 4 LEDs:  2
green and 2 orange(amber) The three cases have a Power lens and a Globe
lens.  Each Lens has a Green LED and an Orange LED.  The DIR-810L dts
only has 3 LED entries
entries.
        leds {
                compatible = "gpio-leds";

                led_power_green: power_green {
                        label = "dir-810l:green:power";
                        gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
                };

                wan {
                        label = "dir-810l:orange:wan";
                        gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
                };

                power_orange {
                        label = "dir-810l:orange:power";
                        gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
                };
        };

I think there should be a dir-810l:green:wan on GPIO 10 or 11 or 14 or
15. I suspect Roger's DIR-810L Globe is not fully functional and would
like to confirm with him and potentially work with him on a common fix
for both.  Feel free to forward my email address to Roger.

>
>>
>> 2)  I think it would be possible for both the DIR-810L and TEW-810DR to
>> have factory.bin.  Presently, a factory image is needed for initial
>> installation and is produced using Cameo
>> cameo/ncc/hostTools/ncc_att_hwid tool.  This tool is difficult to use as
>> it requires 32bit libs and full paths to implement.  Essentially the
>> following string needs to be appended to the sysupgrade image:
>> "	TEW-810DR
1.1RWW1.0
>1.13B04
>
>If you think it's easy, include it in your patch already. Otherwise, first provide sysupgrade support and then provide factory in a second step.
>
>Obviously, not having a factory image will make writing flashing instructions more complicated.
>
>Best
>
>Adrian
>
>
>

-- 
J. Scott Heppler

Penguin Innovations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 


NOTICE: This e-mail message and any attachments may
contain legally privileged and confidential information intended
solely for the use of the intended recipients. If you are not an
intended recipient, you are hereby notified that you have
received this message in error and any review, dissemination,
distribution, copying, or other unauthorized use of this email
and any attachment is strictly prohibited. If you have received
this email in error, please notify the sender immediately and
delete the message and any attachments from your system.

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel