From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: 张鹏 <1805692831@qq.com>
Subject: Re: openwrt batman-adv
Date: Tue, 24 Dec 2019 10:03:10 +0100 [thread overview]
Message-ID: <2363117.f9ZONqFbmS@sven-edge> (raw)
In-Reply-To: <tencent_01E5105A2CC20B1B047FF188EFCF47E55D08@qq.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Tuesday, 24 December 2019 09:37:12 CET 张鹏 wrote:
> Hi,
> The platform I work on is openwrt mips, the kernel I use is version 3.3; the version using batman is relatively low, and I want to use the newer version batman on version 3.3, but I encounter many problems during compilation, and I don't know it Whether it works ?
We dropped the support for kernels lower than 3.16.80 a long time ago [1]. It
is irresponsible to still ship such an old kernel (and batman-adv) version
with known security problems. And the last OpenWrt version which used 3.3 was
something like 12.09 (Attitude Adjustment) from 2013. It is isn't supported by
OpenWrt upstream since many year.
Please tell your hardware (+software) supplier to provide an up-to-date
software package for your system. But since it is OpenWrt, you should just
grab 19.07 [2] and use it - and if it is just a OpenWrt fork and the hardware
supplier never submitted the support to the official OpenWrt then please tell
your hw supplier to get the support correctly integrated in OpenWrt.
Kind regards,
Sven
[1] https://git.open-mesh.org/batman-adv.git/commit/7ab78d556b343b592aa80f4d84b2dfd14019f2d8
[2] https://downloads.openwrt.org/releases/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-24 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 8:37 openwrt batman-adv =?gb18030?B?1cXF9A==?=
2019-12-24 9:03 ` Sven Eckelmann [this message]
[not found] ` <tencent_CA5610319E19CB95CA9DB432847536DEFF09@qq.com>
2019-12-28 5:40 ` 回复： " 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=2363117.f9ZONqFbmS@sven-edge \
--to=sven@narfation.org \
--cc=1805692831@qq.com \
--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