public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] RFC: Removing one indirection layer for patches
Date: Wed, 5 Dec 2012 14:12:21 +0100	[thread overview]
Message-ID: <20121205131221.GA29818@pandem0nium> (raw)
In-Reply-To: <20121205113927.GF26922@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]

Hello Andrew,

just a few comments:

On Wed, Dec 05, 2012 at 12:39:27PM +0100, Andrew Lunn wrote:
> > The biggest different is the "lets install a whole kernel to test this change" 
> > methodology ;)
> 
> Yes, i generally do that, test a whole kernel, not a module. But...
> 
> > Usually (please correct me) batman-adv is developed outside the kernel because 
> > it is easier to test stuff and it worked till now. No one of us wants to port 
> > the latest OpenWrt to the -rc kernel to test stuff ;)
> 
> Do you actually need to port to OpenWrt?

Most people I know using batman-adv use either OpenWRT based routers, some others
"normal" (or stripped down versions of) distributions like Debian. So yes, this
is probably the biggest user base (from my point of view, at least, no surveys
done yet).

> 
> How i work is build a kernel, with everything i need built in. No
> modules. Then tftpboot the kernel, and use the rootfs from the
> disk. Why not do the same with OpenWrt?

OpenWRT has many other non-batman-related patches (platform paches, wifi patches,
...), and upgrading the kernel is a major hassle - you'd need to adapt/port lots
of these patches, and some of them are not as nice as we are used from our Linux
git repos. :)

We try to keep repositories up to date for our OpenWRT users, but this shouldn't
make us or them update the kernel all the time. BTW, OpenWRT also uses compat-wireless
for wifi with custom patches, this is how they keep at the "bleeding edge". If we
change to this style, we would probably have to follow the same pattern.

Cheers,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-12-05 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 21:50 [B.A.T.M.A.N.] RFC: Removing one indirection layer for patches Sven Eckelmann
2012-12-04 23:01 ` Antonio Quartulli
2012-12-05  9:45   ` Sven Eckelmann
2012-12-05 10:35 ` Andrew Lunn
2012-12-05 11:06   ` Antonio Quartulli
2012-12-05 11:24     ` Andrew Lunn
2012-12-05 11:32       ` Antonio Quartulli
2012-12-05 11:23   ` Sven Eckelmann
2012-12-05 11:39     ` Andrew Lunn
2012-12-05 12:05       ` Antonio Quartulli
2012-12-05 13:12       ` Simon Wunderlich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-05 17:40 Marek Lindner
2012-12-05 17:50 ` Sven Eckelmann
2012-12-05 18:04 ` Sven Eckelmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121205131221.GA29818@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox