On Thursday 16 April 2009 01:28:25 Daniel Dickinson wrote: > On Sun, 12 Apr 2009 16:48:57 +0200 > Michael Buesch <[email protected]> wrote: > > > Hi, > > > > I tweaked the HairyDairyMaid-wrtdebrick utility a bit to improve its > > speed. (also changed a few other things like introducing standard > > getopt support). > > > > On my machine (ppc64) the tool is about 60% faster now, if the > > --ludicrous-speed option is used. But it's also a lot faster without > > using this option (about 30%). > > > > Note that usage of --ludicrous-speed might corrupt data on some > > combination of embedded device and host computer. But you can test > > this by doing a few runs _without_ --ludicrous-speed. It will tell > > you at the end whether the run would have corrupted data if > > --ludicrous-speed was used. > > > > There's also an optional kernel accelerator module which does the > > lowlevel bitbanging. This reduces syscall overhead. It brings about > > 3-4% speedup. > > > > The tool can be found here: > > git clone http://git.bu3sch.de/git/wrt-debrick.git > > > > Have fun! :) > > > > PS: Note that the tool will be too fast for very old and slow devices > > now (WRT54G version 1). But if you have a fast PC, the original > > debrick tool is too fast for these devices, too. I will introduce > > optional well defined slowdown functions for this later, so success > > will not depend on the machine speed anymore. > > > > Can you integrate the changes I made > (resulting zip at > http://www.cshore.is-a-geek.com/~cshore/libre/openwrt/HairyDairyMaid_WRT54G_Debrick_Utility_v48~cshore2.zip) >
"Iceweasel can't find the server at www.cshore.is-a-geek.com." > and offer the option of /slow_host or something like that for > backwards-compatibility? The tool is fully backwards compatible, if you don't use the --ludicrous-speed and --noerasedelays options. If you have a very slow device (or very fast host) you might need the new --tckdelay option with something like 3usec delay. But you'd also need that for the original debrick tool. (I have a machine that's too fast for flashing a WRT54G version 1 with the original tool. This issue is solved by the --tckdelay option of my fork). So no compatibility option is needed. The speed improvements when running the tool without --ludicrous-speed and without --noerasedelays come from optimized lowlevel bitbanging and reduced systemcall overhead. There are no semantical changes. And with the --tckdelay option you can "gain" the old slow speed again, if it's needed for your slow WRT device. -- Greetings, Michael. _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
