ath79: add support for D-Link DIR-842 C2#2259
ath79: add support for D-Link DIR-842 C2#2259programmingisart wants to merge 1 commit intoopenwrt:masterfrom programmingisart:master
Conversation
|
The mac address printed on the label is used by LAN |
|
The printed on label mac normally is used on wan, unless many macs are printed. |
But in the devconf partition, the mac printed on label is lan mac also. |
|
The main idea with macs is to keep stock firmware behavior. So after you flash Openwrt, macs stay the same. |
|
In many cases you can find 1 or 2 macs in flash partitions. But you need to Ethernet and two wireless macs that are produced by incrementing the "base" macs some ways. There are functions in user space scripts for that. |
The devconf partition already has something like: lanmac=XX:XX:XX:XX:XX:XX,wanmac=YY:YY:YY:YY:YY:YY So I think the mac printed on label is intended to be lanmac by d-link? |
|
@blocktrron |
|
Tested & working |
blocktrron
left a comment
blocktrron
left a comment
There was a problem hiding this comment.
Hopefully, the last iteration.
Thanks for you work 👍
Hardware spec of DIR-842 C2: SoC: QCA9563 DRAM: 128MB DDR2 Flash: 16MB SPI-NOR Switch: QCA8337N WiFi 5.8GHz: QCA9888 WiFi 2.4Ghz: QCA9563 USB: 2.0 Flash instructions: 1. Upgrade the factory.bin through the factory web interface or the u-boot failsafe interface. The firmware will boot up correctly for the first time. Do not power off the device after OpenWrt has booted. Otherwise the u-boot will enter failsafe mode as the checksum of the firmware has been changed. 2. Upgrade the sysupgrade.bin in OpenWrt. After upgrading completes the u-boot won't complain about the firmware checksum and it's OK to use now. 3. If you powered off the device before upgrading the sysupgrade.bin, just upgrade the factory.bin through the u-boot failsafe interface and then goto step 2. Signed-off-by: Jackson Lim <[email protected]>
|
All done, thanks! |
|
@hanipouspilot @jackcolentern You were disagreeing on the label MAC. Is it lan (eth0.1) or wan (eth0.2)? |
|
@adrianschmutzler It is used by eth0.1 (lan) |
|
I can confirm the LAN and WAN addresses are set exactly the same as the factory D-link firmware |
|
LGTM. However, i would be interested where (Country) you bought this device, as i was only able to find Information about rev. C1 & C3 here (and both lack an USB port). |
Maybe it makes sense to support both devices by making a common dtsi and removing USB from C1? |
|
@jackcolentern But the device is explictly labled as C2? Otherwise, I like the idea of @hanipouspilot but if this is not something you would like to do I'm fine going without C1 support here. So add insult to injury, there seems to be a rev. C3 already. |
If we have the dtsi for dir-842, someone who has C3 can easily test and add it later. |
|
@blocktrron How about we use this PR first, and I will try to get a C3 and find out what hardware it uses, if possible I will make a PR supporting C1 C2 C3 in one go in the future (no promise though). |
5 participants
Hardware spec of DIR-842 C2:
SoC: QCA9563
DRAM: 128MB DDR2
Flash: 16MB SPI-NOR
Switch: QCA8337N
WiFi 5.8GHz: QCA9888
WiFi 2.4Ghz: QCA9563
USB: 2.0
Flash instructions:
failsafe interface.
The firmware will boot up correctly for the first time.
Do not power off the device after OpenWrt has booted. Otherwise the u-boot
will enter failsafe mode as the checksum of the firmware has been changed.
After upgrading completes the u-boot won't complain about the firmware
checksum and it's OK to use now.
upgrade the factory.bin through the u-boot failsafe interface and then goto
step 2.
Signed-off-by: Jackson Lim [email protected]