From: "Franz Böhm" <fboehm@aon.at>
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: Tue, 04 May 2010 13:13:18 +0200 [thread overview]
Message-ID: <4BE0014E.8080204@aon.at> (raw)
In-Reply-To: <201005041021.30248.lindner_marek@yahoo.de>
Of course you are right Marek. I don't want to stay with 2.6.14 and will
switch to a kernel >2.6.21 asap.
I wanted to say that it's suddenly more a general problem using chip
supplier or third party SDK's for embedded systems and being constrained
to use quite old kernels.
Regards,
Franz
Marek Lindner schrieb:
> Hi,
>
>> Marek, i've tested your patches with all major kernel releases from 2.6.20
>> to 2.6.33. What i have seen is:
>>
>> * 2.6.20 fails for various reasons
>> * 2.6.23 and 2.6.24 show some warnings
>> * all other kernel versions are fine
>>
>> The warnings for 23 and 24 can be fixed by moving the *_read() defines
>> from "< 2.6.25" to "< 2.6.23". If you integrate this modification into
>> your patch, you will gain my blessing and my sign-off. :)
>
>
> thanks for testing. I followed your suggestion before pushing the patches. :)
>
> Since 2.6.20 does not work at this point I removed it from the list of
> supported kernel versions. Unfortunately, many embedded system vendors do not
> bother to bring their drivers upstream and instead, publish "code blobs"
> limited to an old linux version. So, it makes sense for us to offer support for
> older versions as well. We could remove old versions if the effort is getting
> too high (as we just did with 2.6.20).
>
> @Franz: I know you are stuck at 2.6.14 or something similar with your Atheros
> system but I don't think it is feasible for us to "go down" that far (unless
> you find a way). It might be easier to try pushing your Atheros beyong the
> current 2.6.21 minimum.
>
> Regards,
> Marek
>
next prev parent reply other threads:[~2010-05-04 11:13 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
2010-05-03 20:40 ` Simon Wunderlich
2010-05-04 2:21 ` Marek Lindner
2010-05-04 11:13 ` Franz Böhm [this message]
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=4BE0014E.8080204@aon.at \
--to=fboehm@aon.at \
--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