From: Andrew Lunn <andrew@lunn.ch>
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.] sysfs compat
Date: Mon, 3 May 2010 10:03:01 +0200 [thread overview]
Message-ID: <20100503080301.GE10849@lunn.ch> (raw)
In-Reply-To: <201005030828.08856.lindner_marek@yahoo.de>
> At some point we have to start thinking about how many versions we
> want to support. Each new kernel brings more changes which need to
> be dealt with. Right now, the required effort is still at a
> sustainable level but the gap is growing. On one hand it is a nice
> playground to expand our knowledge about macros and demonstrate what
> nasty things you can do (see the second patch as an example). ;-)
> On the other hand it always requires a serious amount of time and
> effort. It only makes sense if at least some people are using
> it. Opinions ?
I guess the problem here is devices which cannot use modern kernels.
Why can a device not use a modern kernel?
1) Binary only drivers which work only for a specific kernel. I guess
the biggest problem here is broadcom devices? What is the current
state here? How good is the native linux broadcom driver? Are there
other chipsets without an open driver?
2) The need to use a vendor kernel since the mainline kernel does not
have the necessary support. How big a problem is this?
What other reasons are there not to use a modern kernel?
Andrew
next prev parent reply other threads:[~2010-05-03 8:03 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 ` Andrew Lunn [this message]
2010-05-03 9:05 ` [B.A.T.M.A.N.] " Franz Böhm
2010-05-03 10:30 ` Sven Eckelmann
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=20100503080301.GE10849@lunn.ch \
--to=andrew@lunn.ch \
--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