7ae59a2f288ba1cef23b20e1d36e199e8c646245 working fine!
Where is the link to the new build that fixes the winbond issue?
If you mean a snapshot image, there isn't one as the above commit has not yet been pushed to master. So currently, you either have to build an image with the commit applied, or take one from a community member. There are builds to be had by following the Stuff link found by clicking my avatar.
Does anyone know when there will be a snapshot image available for the winbond issue? Thanks.
When that commit finds its way into master. Best to ask the owner of that github/staging tree when it might get pushed.
Here are the images I've built form https://git.openwrt.org/openwrt/staging/kaloz.git
, commit 7ae59a2f288ba1cef23b20e1d36e199e8c646245
openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin
I only have tested the factory img.
https://cdn.corifeus.com/openwrt/SNAPSHOT/targets/mvebu/generic/
this is kaloz's staging repo, with all packages.
imo, the best way to get a winbond build for the recent rango units is to add the patch to a current clone of master, not to build a ~5 week old(4.9) staging tree YMMV.
I am new at this patching thing. I am trying to get LEDE 17.01.4 working on my new WRT3200ACM. Do you know where I can find a clone for this specific version?
Sorry, no, I just run master as it is stable enough for my purposes. If push comes to shove, there are images off the Stuff link on my avatar.
Thanks! Will look into it.
Here are the images I've built form https://git.openwrt.org/openwrt/staging/kaloz.git
, commit 7ae59a2f288ba1cef23b20e1d36e199e8c646245
openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin
sha256
1d0b208cbf4845a0a6e95d65daa9f72e2001802f4499393d871186075dc54f21 openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
e415531f268ebcc2e8e5dac3b687f9b9c5f1ca95104e10799bf4b69bfe80ed8c openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin
md5
e62398c625198fbd0cb428a220f0815b openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
9879eef008969a99c70f8e8910dab348 openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin@tmomas / @hnyman Any chance the WRT3200ACM 17.01.4 stable image could be updated with kaloz's
3 patches?
Right, but that doesn't affect any 17.01.4 Stable images, hence why I asked for the the Stable images for the WRT3200ACM to be updated.
Does Kaloz's patches change anything other than allowing for the WinBond chip to be recognized and partitioned accordingly?
- If not, there doesn't seem to be a reason to not regenerate the two Stable images for the WRT3200ACM with those patches applied.
- These patches are a bit different than most other patches, as without them, the firmware cannot be installed to WRT3200ACM's with WinBond NAND flash because the ROM isn't recognized.
Because it takes effort, and the next stable is in the works.
Edit: I'm not about to waste my time enumerating all the blatant flaws with this. I will point out what your keen observational skills apparently have overlooked; note the monikers from the linked ML as the ones responsible for the buildbots, try barking up that tree. Nice numbers though, what part of your anatomy did you pull those from.
Does it need to be done manually? Yes. Does it take significant time? No.
Perhaps it's believed this is more complex than it really is?
- Copy patches to the appropriate directory, ensure kernel makefile has the same 4.4.92 kernel set, then issue
make... takes all of 3min to issue and verify, ~15min to build.
- Copy the two newly generated images to web server... takes all of 2min
- Update sha256 hashes for the images... takes all of 30s to copy and paste.
- Time required:
- User: ~5min
- Total: ~20min
What's weird is I can't install DD-WRT on my WRT3200ACM but not LEDE. I want my damn cake and piece_of_cake!