However, I cannot find any reference to an A2 being made? Does anyone else have a D-Link DIR-2660 and know if there are multiple revisions? And if the A2 is usable with OpenWRT?
looking at some of the dlink web sites they only say ver.A
I would look through the current firmware for indicators that it may say A1 or A2
if that is no help
also thing i would do is download version of firmware like this https://support.dlink.com/ProductInfo.aspx?m=DIR-2660-US
I'd get versions above 1.04 as this is what is shipped
I would see if this version is accepted as dlink should protect you if it's not
this would give you more information about this
there have been people saying that openwrt won't flash on there DIR-2660
now I'm wondering if they have the A2 and never checked
I think from what is shown it takes the same firmware as the one labeled A1
you could test this by uploading a downloaded version that says it's for the A1
Post your text output as actual text please, so it's searchable. Screenshots cannot be indexed by any search engine, you see.
No, you're on a DSA target. The software bridge is there (br-lan). For now there's no LuCI counterpart yet, but you can manipulate it on the command line if needed.
they all require new headers due to your boot loader now requiring them now
I have not done this but you should be able to extract the kernel image from a sysupgrade file
edit it the same & place it back into the archive "sysupgrade file"
well it seems the later DIR-2660-A1's needs this as well
I think as some point they updated the boot loader
it would be better if this mod was added for all the devices
that is the one's built by SGE DIR-878,867,882,1960,2660 & others
it wasn't added due to it not being needed at the time
but it would help in future is someone writes the encrypt part
with would make them web flashable
you could contact them i think it would speed up everything
it would take me a long time to lean how & then another 6 mouths for the commit to got thought
there is a part where \tools\firmware-utils\src\uimage_padhdr.c
add's padding to the standard uboot header
"96 bytes of 00 in this case"
as this area is the part added maybe this is where the
DEVICE_MODEL & DEVICE_VARIANT
from target\linux\ramips\image\mt7621.mk
should be added
I think the only option for the time being is to keep modifying the factory image
I'm going to play in the background
but someone who know what they are doing could do it in a few minutes
I can read the code ok but not so good at writing it