I'm not understanding well your advices...
What should we do for try our own changes in the code of batman-adv?
You should just clean the batman-adv part of openwrt after each change instead of compiling everything again. You can for example modify the prepare part of the Makefile script of the batman-adv openwrt package to copy the .c/.h/.sh/Makefile* from your development folder. At least Martin did this (or at least something similar).
Do you mean that I should modify the makefile (my path to this makefile is .../backfire/trunk/feeds/packages/net/batman-adv/Makefile)so instead the download the code of batman-adv, it compile my own code?
A simple `make package/batman-adv/{clean,prepare,compile,install}` after each test change would be enough to just get the new code, recompile the batman-adv module and to generate a ipk package for batman-adv. This ipk file can be copied to your testnode and installed using `opkg instal *.ipk`. The new module will be loaded after a restart.
But an initial compile of the OpenWRT target kernel is still necessary.
Btw. you can get write access to the batman git repositories when you like to.
But, how can I compile only the batman module and generate ipk package? If I compile directly the batman-adv code, the batman-adv.ko module does not work in the testnode. Can I generate a batman-adv ipk package with out compile the whole openwrt?
Sorry for my thickness ;-)