commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Building-with-openwrt (0c5a30eb)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Building-with-openwrt (f65026c7)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit f65026c7d1858fad648d05c05d350a724ac0ef12 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Thu Jan 5 16:53:35 2012 +0000 doc: batman-adv/Building-with-openwrt >--------------------------------------------------------------- f65026c7d1858fad648d05c05d350a724ac0ef12 batman-adv/Building-with-openwrt.textile | 39 +++++++++++++++----------------- 1 file changed, 18 insertions(+), 21 deletions(-) diff --git a/batman-adv/Building-with-openwrt.textile b/batman-adv/Building-with-openwrt.textile index bf372eb7..c8f6bea9 100644 --- a/batman-adv/Building-with-openwrt.textile +++ b/batman-adv/Building-with-openwrt.textile @@ -1,12 +1,12 @@ -h1. Building B.A.T.M.A.N. Advanced with OpenWRT +h1. Building B.A.T.M.A.N. Advanced with OpenWrt -Many tutorials assume that you have batman-adv running on an OpenWRT system without going into detail how to get the system built and configured. This documents aims to fill the gap by providing a step-by-step explanation how to get your OpenWRT system up & running. +Many tutorials assume that you have batman-adv running on an OpenWrt system without going into detail how to get the system built and configured. This documents aims to fill the gap by providing a step-by-step explanation how to get your OpenWrt system up & running. h2. Getting the OpenWRT build environment -First, you need to obtain a copy of the OpenWRT build system which contains all the build information to compile & package a complete linux system. You can either checkout the last stable or the trunk directly from the OpenWRT SVN repository or get tarballs from the OpenWRT project website. We assume you intend to download the latest stable (backfire 10.03 at the point of writing this document) via SVN: +First, you need to obtain a copy of the OpenWrt build system which contains all the build information to compile & package a complete Linux system. You can either checkout the last stable or the trunk directly from the OpenWrt SVN repository or get tarballs from the OpenWrt project website. We assume you intend to download the latest stable (backfire 10.03 at the point of writing this document) via SVN: <pre> svn co svn://svn.openwrt.org/openwrt/tags/backfire_10.03 openwrt @@ -19,7 +19,7 @@ cd openwrt make menuconfig </pre> -+Note+: The batman-adv package is not there yet because it needs to be activated seperately (see the following steps). ++Note+: The batman-adv package is not there yet because it needs to be activated separately (see the following steps). To build your images you always have to invoke the "make" command from within the openwrt folder: @@ -29,29 +29,27 @@ cd openwrt make </pre> -The rest of the document will focus on the batman-adv package. It is assumed that you configured the system to work on your platform. If you require additional information on how to tweak your OpenWRT system, please see "the OpenWRT project website":http://www.openwrt.org. +The rest of the document will focus on the batman-adv package. It is assumed that you configured the system to work on your platform. If you require additional information on how to tweak your OpenWrt system, please see "the OpenWrt project website":http://www.openwrt.org. h2. Adding the batman-adv package -The standard OpenWRT package feed contains a batman-adv package which is intended to be used on a day to day basis, therefore it retrieves the latest batman-adv stable release. Since a lot of people want to experiment with the latest features or use OpenWRT to test their own batman-adv patches we also provide an openwrt package feed which contains the batman-adv development version. +The standard OpenWrt package feed contains a batman-adv package which is intended to be used on a day to day basis, therefore it retrieves the latest batman-adv stable release. Since a lot of people want to experiment with the latest features or use OpenWrt to test their own batman-adv patches we also provide an OpenWrt package feed which contains the batman-adv development version. -h3. Adding the stable version - +stable version: <pre> scripts/feeds update scripts/feeds install kmod-batman-adv </pre> -_Note_: If you downloaded an OpenWRT release but intend to build the latest batman-adv package you might need to modify your feeds.conf(.default). Make sure you have _"svn-src packages svn://svn.openwrt.org/openwrt/packages"_ instead of e.g. _"src-svn packages svn://svn.openwrt.org/openwrt/branches/packages_8.09"_. - ++Note+: If you downloaded an OpenWRT release but intend to build the latest batman-adv package you might need to modify your feeds.conf(.default). Make sure you have "svn-src packages svn://svn.openwrt.org/openwrt/packages" instead of e.g. "src-svn packages svn://svn.openwrt.org/openwrt/branches/packages_8.09". -h3. Adding the developer version +developer version: -Append the following line to your openwrt feed configuration file (either feeds.conf or feeds.conf.default): +Append the following line to your OpenWrt feed configuration file (either feeds.conf or feeds.conf.default): <pre> src-svn batman http://downloads.open-mesh.org/svn/openwrt-feed/ @@ -71,7 +69,7 @@ h2. Configuring the batman-adv package As soon as the batman-adv package has been added, it will show up in the OpenWRT package menu: -h3. stable version +stable version: <pre> Kernel modules ---> @@ -79,7 +77,7 @@ Kernel modules ---> kmod-batman-adv </pre> -h3. developer version +developer version: <pre> Kernel modules ---> @@ -97,7 +95,7 @@ h2. Rebuilding the package If you experience build problems or simply intend to rebuild the batman-adv package only, you can tell OpenWRT to build a specific package and enable the debugging mode as follows: -h3. stable version +stable version: <pre> cd openwrt @@ -105,7 +103,7 @@ make package/batman-adv/clean make package/batman-adv/compile V=99 </pre> -h3. developer version +developer version: <pre> cd openwrt @@ -119,13 +117,13 @@ h2. Applying patches The package offers an easy way to apply custom patches whenever batman-adv is built. Simply copy your patches into the "patches" folder inside the package directory (you have to create the folder in case it does not exist yet). Patch files having the string 'batman' in their name are applied to batman-adv whereas patches containing the string 'batctl' are applied to the batctl tool. The location of the folder depends on which package you want to patch: -h3. stable version +stable version: <pre> openwrt/feeds/packages/net/batman-adv/patches </pre> -h3. developer version +developer version: <pre> openwrt/feeds/batman/batman-adv-devel/patches @@ -137,8 +135,7 @@ h2. Changing the batman-adv / batctl version It is also possible to modify the batman-adv version if you ever wanted to build an older/newer version than configured in the package: -h3. stable version - +stable version: Adjust the PKG_VERSION variable to download & build the stable release you are interested in. @@ -149,8 +146,8 @@ PKG_VERSION:=2010.0.0 [..] </pre> -h3. developer version +developer version: Adjust the PKG_BATMAN_REV variable for batman-adv and the PKG_BATCTL_REV variable for batctl to download & build the git revision you are interested in:

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Using-batctl (a97a7b18)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit a97a7b1890fec529bc8ad668f12ff72511c2f204 Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Fri Dec 2 17:19:24 2011 +0000 doc: batman-adv/Using-batctl >--------------------------------------------------------------- a97a7b1890fec529bc8ad668f12ff72511c2f204 batman-adv/Using-batctl.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index 6060ea22..0c44ce68 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -4,7 +4,7 @@ Batctl is the configuration and debugging tool for batman-adv. It is thoroughly h2. Using batctl for configuration -All configuration of batman-adv is done in the virtual filesystem _sysfs_ and batctl is merely an convenient interface to this. +All configuration of batman-adv is done in the virtual filesystem _sysfs_ and batctl is merely a convenient interface to this. A quick overview of the config options available with batctl: * Add and remove interfaces to the mesh network.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/NetworkCoding-technical (c4a3cafa)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit c4a3cafa814eb4d19a110c51da9017f4eea55596 Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Tue Dec 6 10:31:04 2011 +0000 doc: batman-adv/NetworkCoding-technical >--------------------------------------------------------------- c4a3cafa814eb4d19a110c51da9017f4eea55596 batman-adv/NetworkCoding-technical.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/NetworkCoding-technical.textile b/batman-adv/NetworkCoding-technical.textile index b6025289..e8291e2d 100644 --- a/batman-adv/NetworkCoding-technical.textile +++ b/batman-adv/NetworkCoding-technical.textile @@ -30,7 +30,7 @@ To make the implementation of catwoman complete, the following features must be * -Use the link quality of overhearing links when looking for coding opportunities.- * -Support configuration with batctl.- * -Use bat_dbg instead of printk.- -* Support setups with multiple interfaces. +* Support setups with multiple interfaces. (Need to make sure that nc_nodes are on the same interface.) * -Maintain ref-counters for struct orig_node.- * -Refactor code into three files: catwoman.c, coding.c, and decoding.c- * -Remove nc_path after a certain timeout.-

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Experience (38d1e54e)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Using-batctl (21cb3904)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 21cb3904bd0facee3d7e69f0e305d465722c3b48 Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Fri Dec 2 17:23:15 2011 +0000 doc: batman-adv/Using-batctl >--------------------------------------------------------------- 21cb3904bd0facee3d7e69f0e305d465722c3b48 batman-adv/Using-batctl.textile | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index e5e12136..dcc86707 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -18,12 +18,9 @@ batctl offers a great deal of tools for monitoring the state of your mesh node/n * Parse logfiles to discover routing loops. * Retrieve live information from the batman-adv module. -To retrieve information, you must compile your kernel with debugfs (it usually is by default) and mount your debugfs: -<pre> -mount -t debugfs none /sys/kernel/debug -</pre> +To retrieve information, you must compile your kernel with debugfs (it usually is by default) -With debugfs mounted, you can use batctl to, among others, seeing the following: +With debugfs compiled in, you can use batctl to, among others, seeing the following: * A list of other mesh nodes in the network (originators). * Lists of none-mesh nodes connected to the network (clients or neighbors). * A list of available gateways in the network.

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/SubmittingLinux: Remove the linux-next part which was only necessary for GregKH submissions (ea441816)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit ea4418163608e703c75dc9dfe6d218f1fc749c94 Author: Sven Eckelmann <sven(a)narfation.org> Date: Fri Dec 23 22:04:33 2011 +0000 doc: batman-adv/SubmittingLinux: Remove the linux-next part which was only necessary for GregKH submissions >--------------------------------------------------------------- ea4418163608e703c75dc9dfe6d218f1fc749c94 batman-adv/SubmittingLinux.textile | 67 ++++++++------------------------------ 1 file changed, 14 insertions(+), 53 deletions(-) diff --git a/batman-adv/SubmittingLinux.textile b/batman-adv/SubmittingLinux.textile index 34f3a5da..8b074e43 100644 --- a/batman-adv/SubmittingLinux.textile +++ b/batman-adv/SubmittingLinux.textile @@ -11,20 +11,16 @@ Following steps must always be done: * check difference with standalone/next * rebase on top of previous version * squash/cleanup patches -* check if all versions compile cleanly against a current version of linux-next and sparse (cgcc) +* check if all versions compile cleanly using sparse (cgcc) * format patches * check commit messages author/signed-off-by of patches (Cc: stable(a)kernel.org for important bugfixes for older kernel) * Add "batman-adv: " before each commit subject -* get current version of linux-next -* create working branch on linux-next -* apply all patches on linux next -* check if all patches build again with linux next * check if all patches are checkpatch.pl clean * submit patches -h2. get the linux-integration and linux-next repository +h2. get the linux-integration repository <pre> @@ -33,11 +29,6 @@ Initialized empty Git repository in /home/batman/linux-merge/.git/ remote: Counting objects: 1544059, done. remote: Compressing objects: 100%25 (252781/252781), done. .... -'-(%25)-> git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git -Initialized empty Git repository in /home/batman/linux-next/.git/ -remote: Counting objects: 1544059, done. -remote: Compressing objects: 100%25 (252781/252781), done. -.... '-(%25)-> cd linux-merge </pre> @@ -263,6 +254,16 @@ Switched to branch 'patches' </pre> + +h2. check if all patches build cleanly + +It must be checked whether it builds with allnoconfig (@+NET@,@+CRC16@,@+/-MODULES@) as module/builtin and allyesconfig as module/builtin + +<pre> +'-(%25)-(patches)> make +.... +</pre> + h2. format patches @@ -281,50 +282,11 @@ h2. format patches Usually I add "batman-adv: " right when checking the signed-off-by and author (from) line. Patches which are also important bugfixes for older kernels (Kernel-Oops, Deadlock, ...) must also submitted to stable(a)kernel.org. It is done by adding "Cc: stable(a)kernel.org" to this patch. -h2. apply all patches on linux next - - -<pre> -'-(%25)-(patches)> cd ../linux-next -'-(%25)-(master)> git remote update -'-(%25)-(master)> git reset --hard origin/master -HEAD is now at c3116ae Add linux-next specific files for 20100625 -'-(%25)-(master)> git checkout -b davem -Switched to a new branch 'davem' -'-(%25)-(davem)> git am -3 ../linux-merge/00*.patch -Applying: batman-adv: Convert names from Java to C style -Applying: batman-adv: Avoid rounding issues for local hna timeout -Applying: batman-adv: Lower resolution for timeouts -Applying: batman-adv: replace manual calculation by msecs_to_jiffies() for better readability -Applying: batman-adv: Add sysfs abi documentation about bonding -Applying: batman-adv: adapting source version to revised versioning scheme -Applying: batman-adv: Add include guards to all header files -</pre> - - -h2. check if all patches build again with linux next +h2. checkpatch patches -It must be checked whether it builds with allnoconfig (@+NET@,@+CRC16@,@+/-MODULES@) as module/builtin and allyesconfig as module/builtin <pre> -'-(%25)-(davem)> make -.... -</pre> - - -h2. format patches on top of linux-next master - - -<pre> -'-(%25)-(davem)> git format-patch -s --patience -M master -0001-batman-adv-Convert-names-from-Java-to-C-styl.patch -0002-batman-adv-Avoid-rounding-issues-for-local-h.patch -0003-batman-adv-Lower-resolution-for-timeouts.patch -0004-batman-adv-replace-manual-calculation-by-mse.patch -0005-batman-adv-Add-sysfs-abi-documentation-about.patch -0006-batman-adv-adapting-source-version-to-revise.patch -0007-batman-adv-Add-include-guards-to-all-header-.patch -'-(%25)-(davem)> ./scripts/checkpatch.pl --strict 00*.patch +'-(%25)-(patches)> ./scripts/checkpatch.pl --strict 00*.patch total: 0 errors, 0 warnings, 0 checks, 135 lines checked 0001-batman-adv-Convert-names-from-Java-to-C-styl.patch has no obvious style problems and is ready for submission. @@ -353,7 +315,6 @@ h2. submit patches <pre> -'-(%25)-(davem)> ../linux-merge/ '-(%25)-(patches)> git checkout batman-adv/next '-(%25)-(batman-adv/next)> git rev-parse batman-adv/next 12513b76a021e5b41a9d5d5981da75dfd6480890

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo: Reset release todo (5e16dd14)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 5e16dd14f53c3284f6d8c9d90236475dc7d1a069 Author: Sven Eckelmann <sven(a)narfation.org> Date: Fri Dec 23 21:59:29 2011 +0000 doc: batman-adv/Release-todo: Reset release todo >--------------------------------------------------------------- 5e16dd14f53c3284f6d8c9d90236475dc7d1a069 batman-adv/Release-todo.textile | 46 ++++++++++++++++++++--------------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 5978bd93..b32b94c1 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -14,41 +14,41 @@ h2. Release Scheduling h2. Code -* [x] make sure all code contains the release version strings -* [x] update copyright years (if needed) -* [x] remove dead code (if any) -* [x] check against kernel versions -* [x] check that maint branch is merged in next -* [x] check for open patches on the ml -* [x] git tag release +* [ ] make sure all code contains the release version strings +* [ ] update copyright years (if needed) +* [ ] remove dead code (if any) +* [ ] check against kernel versions +* [ ] check that maint branch is merged in next +* [ ] check for open patches on the ml +* [ ] git tag release h2. Documentation -* [x] build changelog -* [x] update README -* [x] write release announcement -* [x] update wiki documentation +* [ ] build changelog +* [ ] update README +* [ ] write release announcement +* [ ] update wiki documentation h2. Release -* [x] build package tar.gz and generate checksums -* [x] move packages/checksums to stable/sources / create symlinks from releases -* [x] update download links in the redmine downloads page -* [x] send release mail -* [x] update IRC channel topic +* [ ] build package tar.gz and generate checksums +* [ ] move packages/checksums to stable/sources / create symlinks from releases +* [ ] update download links in the redmine downloads page +* [ ] send release mail +* [ ] update IRC channel topic h2. Distributions -* [x] update openwrt package -* [x] update debian package +* [ ] update openwrt package +* [ ] update debian package h2. Aftershow -* [x] Merge next into master branch (to get changes on README, CHANGELOG, ...) -* [x] Merge current git tag into maint (must be fast-forward or pre-tagging steps were done wrong) -* [x] Merge patches from master into next (to get all the fancy new features) -* [ ] Rebase patches in next on top of linux-next and send it to kernel maintainers for future kernels ([[SubmittingLinux]]) -* [x] re-enable next check in checkstuff.sh +* [ ] Merge next into master branch (to get changes on README, CHANGELOG, ...) +* [ ] Merge current git tag into maint (must be fast-forward or pre-tagging steps were done wrong) +* [ ] Merge patches from master into next (to get all the fancy new features) +* [ ] Rebase patches in next on top of last linux -rc1 and send it to kernel maintainers for future kernels ([[SubmittingLinux]]) +* [ ] re-enable next check in checkstuff.sh

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Using-batctl (d956ab92)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit d956ab92435426098dc188dd7fd84eb7a9280e02 Author: Martin Hundebøll <martin(a)hundeboll.net> Date: Fri Dec 2 17:20:28 2011 +0000 doc: batman-adv/Using-batctl >--------------------------------------------------------------- d956ab92435426098dc188dd7fd84eb7a9280e02 batman-adv/Using-batctl.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Using-batctl.textile b/batman-adv/Using-batctl.textile index 0c44ce68..e5e12136 100644 --- a/batman-adv/Using-batctl.textile +++ b/batman-adv/Using-batctl.textile @@ -23,7 +23,7 @@ To retrieve information, you must compile your kernel with debugfs (it usually i mount -t debugfs none /sys/kernel/debug </pre> -With debugfs mounted, you can use batctl to, among other, seeing the following: +With debugfs mounted, you can use batctl to, among others, seeing the following: * A list of other mesh nodes in the network (originators). * Lists of none-mesh nodes connected to the network (clients or neighbors). * A list of available gateways in the network.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Experience (989fa07e)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017