and here is the reply...
Andrew
---------------------------------------------------------------------- On Tue, Aug 25, 2009 at 10:05:30PM +0200, Andrew Lunn wrote:
Hi Greg
I've decided to take on the challenge of getting batman-advanced into mainline. This is a challenge since as to date all i've had committed to mainline are a few USB querks for devices i happen to have.
B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing protocol for multi-hop ad-hoc mesh networks. It can be used over wireless and wired links. Batman is used for example in Berlin to provide their "Freifunknetzes", free wireless network, and in many other cities.
The project website can be found at:
My first question would be is this something that can go into staging? It is not a device driver or a filesystem which seems to be the major usage for staging.
If it is "self-contained" then we can add it to the staging tree.
The only exception i found to this is the openPOWERLINK protocol stack.
Heh, bad example, that code is getting ripped out for the 2.6.32 release as there has been no support from the developers to get this code into mergable shape :)
Batman layers on top of the wireless and wired network devices, exporting a virtual network device for accessing the resulting mesh. The nice thing about batman is that it is completely contained. It does not need any patches anywhere else, which does fit with the staging model.
Good.
But first off, what is keeping this code from being added to the "main" portion of the kernel tree? Have you submitted it for inclusion there already? If so, what was the response? If not, why not?
The source code is currently in a subversion repository:
http://downloads.open-mesh.net/svn/batman/trunk/batman-adv-kernelland/
I also have a list of things which i think need doing:
Finish stripping out debug_log.
Make batctl, the user space configuration tool, standalone.
Maybe make batctl _The_ tool for configuration and status and depreciate direct /proc access, so that we can restructure it without too much pain for users.
Take out the dot_draw/josm formatting in /proc/net/batman-adv/vis and put it into userspace as part of batctl.
Think if /proc/net/batman-adv should be renamed /proc/net/bat0 giving the option of /proc/net/bat1 etc in the future?
Should /proc/net/batman-adv/interface be replaced with an IOCTL interface similar to brctl?
Maybe move orig_interval, aggregate_ogm and write half of vis to /sys/class/batman/bat0/?
Investigate if there is a generic linux hash algorithm which should be used?
Strip out all backward compatibility support to older kernels.
Make use of printk %pM support.
The code is however sparse clean and checkpatch only complains about a few lines being longer than 80 characters. Most of these are printk like statements.
My second question would be when is the right time to get into staging?
Hm, based on the above, right now :)
Should i work on all these issues first? Or can it go into staging with some of these issues in a TODO file, to be joined by new issues as the code is reviewed by more experts?
Yes, it can go in right now, with that TODO file, and we, and you, can work on it there.
Sound good? If so, send me some patches!
thanks,
greg k-h