public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] sysfs compat
Date: Mon, 3 May 2010 12:30:38 +0200	[thread overview]
Message-ID: <201005031230.45286.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <4BDE91F3.4010209@aon.at>

[-- Attachment #1: Type: Text/Plain, Size: 2358 bytes --]

Franz Böhm wrote:
> Also all Atheros based systems with binary drivers from Atheros itself
> or SDK's from third party vendors only work with particular (quite old)
> kernel versions. Perhaps you are able to build with newer kernel but
> it's much more difficult to get support from the chip manufacturer this
> way.
> 
> Using open source drivers instead is not always an opinion because it's
> very hard to comply with radio regulations and get your product
> certified. This is why I think it's somehow also important for BATMAN to
> support older kernels.

Yes, commercial support is a big problem. The atheros driver (targeted for 
2.6.15) can be ported to with reasonable effort to a kernel supported by 
batman-adv. But as you stated above the upstream support maybe will be gone 
afterward.

...do we really trust devices running really old kernels? There must be a well 
educated and hard working support team behind that kernel to keep it working. 
Not that bugs come over time, but bugs are found over time and must be fixed 
or otherwise some people will have more fun than you with these "features".

So we have different possibilities, but the most important one should be the 
requirements of the actual developers. Both Marek and Simon use batman-adv on 
different kernels and have special requirements on kernel versions they must 
support.

We can use openwrt as extra information what should be supported. Currently I 
see kernels from 2.6.25-2.6.34.

To come back to the security consideration: Usually the kernel folks support 
the last kernel only with security fixes and other bug fixes. This isn't 
sufficient for people which run a specific kernel a long time (distributions 
for example). As result of these requirements a specific kernel version is 
maintained longer than others [1] ("LTS" if you want to name it in ubuntu-
style). So the lowest kernel version number here is 2.6.27

I am not sure if we really want to check kernels of specific desktop/server 
distributions because they aren't our real target audience and kernels of 
distributions with a really long support time tends to have more in common 
with every other kernel but not with the vanilla kernel with the same version 
number.

Best regards,
	Sven

[1] http://www.kroah.com/log/linux/stable-status-01-2010.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-05-03 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03  0:28 [B.A.T.M.A.N.] sysfs compat Marek Lindner
2010-05-03  0:28 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: adding MAC_FMT compatibility Marek Lindner
2010-05-03  0:28 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: adding sysfs compat Marek Lindner
2010-05-03  8:03 ` [B.A.T.M.A.N.] " Andrew Lunn
2010-05-03  9:05   ` Franz Böhm
2010-05-03 10:30     ` Sven Eckelmann [this message]
2010-05-03 20:40 ` Simon Wunderlich
2010-05-04  2:21   ` Marek Lindner
2010-05-04 11:13     ` Franz Böhm
2010-05-04 11:40       ` elektra
2010-05-04 12:36         ` Franz Böhm
2010-05-04 13:05           ` elektra
2010-05-04 17:34             ` Franz Böhm
2010-05-04 23:59             ` RHS Linux User

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=201005031230.45286.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.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