I wonder if there is a way to save me(us) time, and to know in advance --rather than lines inserted/removed or typos described in every changeset-- whether a given build includes a new kernel subversion/patch, and/or a new driver, or something relevant to the hardware, in order to allow me(us) narrow my(our) research in a few set of builds.
Does anybody knows how to tell? _________________ If you want support, please read first the announcements and forum rules.
Si usted desea ayuda, por favor lea primero los anuncios y las reglas del foro.
I wonder if there is a way to save me(us) time, and to know in advance --rather than lines inserted/removed or typos described in every changeset-- whether a given build includes a new kernel subversion/patch, and/or a new driver, or something relevant to the hardware, in order to allow me(us) narrow my(our) research in a few set of builds.
Does anybody knows how to tell?
Wish there was a good/easy answer... But the only real changelog is the svn timeline http://svn.dd-wrt.com
Best bet is to keep an eye on new builds threads... Device specicic threads.... That is also not comprehensive...
hands on/trial and error seems like the best bet (specifically not the answer you wanted)
For popular devices like the r7000 there is a lot of "chatter" on the forums that sheds some light. But other devices (older/less popular) feels more hit and miss.
Generally speaking of course.
i.e. if I had your device I would share my hands on exp, but I dont
That said keep an eye out for chatter on devices that have the same chipsets as yours. while YMMV, you may glean insight on driver enhancements and such.
i.e. even though I have an R6300v2 the R7000 chatter is very helpful to keep up on... Both are BCM ARM CPUs
Also the closer you live to the bleeding edge with your hardware the more you have to read up/keep up on it. A device takes a while after initial support before you see rock solid build recommendations... The R7000 for example just got its new driver and stable WiFi (with no CLI workarounds) earlier just this month.
^^just observations from reading up on these types of forums since the early/mid 2000’s and sorting through it all during several device upgrades and WiFi implementations. (I reserve the right to misinterpret the world around me.) _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Joined: 24 Oct 2008 Posts: 1079 Location: Latin America
Posted: Sun Mar 01, 2015 0:06 Post subject:
I have doing that, but I wonder if there is a more efficient way to use my(our) time.
I mean: to use the svn timeline for track, say, 100 builds would be something like the attached images.
More than I changelog, I would like to read a "milestone" progress (which is empty in the svn).
svn-log.png
Description:
If one want it at a glance, this is the best I've found.
Filesize:
117.19 KB
Viewed:
3401 Time(s)
svn-timeline-diff.png
Description:
To check build differences can be very akward.
Filesize:
144.92 KB
Viewed:
3401 Time(s)
_________________ If you want support, please read first the announcements and forum rules.
Si usted desea ayuda, por favor lea primero los anuncios y las reglas del foro.
You are right... It is all "nightlies"... No formal milestones called out these days (not formally)
The project casts such a wide net across supported devices, that it might be difficult to manage centrally...
I.e. ralink and/or atheros forum sections track some of this in the op of new builds threads (if I recall). But that is done by users.
I thought that was kind of a neat thing to see...
Even in BCM section there are several make files in play... You would likely have to attempt to track at that level.
Given the average dd-wrt user may not be aware of the make file that is used to compile their firmware... Tracking it meaningfully might be lost on the masses.
Plus it might be a lot of new admin overhead that few can really appereciate that ultimately slows the development process.... _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE