From: Chris Paterson <Chris.Paterson2@renesas.com>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>,
Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: RE: [cip-dev] [next] iwg20m: add support for this board
Date: Fri, 7 Jun 2019 15:06:59 +0000 [thread overview]
Message-ID: <TYAPR01MB2285605310C92322737DEB4FB7100@TYAPR01MB2285.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1559918469.21054.3.camel@codethink.co.uk>
Hello,
> From: cip-dev-bounces@lists.cip-project.org <cip-dev-bounces@lists.cip-
> project.org> On Behalf Of Ben Hutchings
> Sent: 07 June 2019 15:41
>
> On Thu, 2019-06-06 at 16:48 +0900, Daniel Sangorrin wrote:
> > This patch adds support for the iwg20m board to isar-cip-core.
> >
> > - Kernel version notes
> >
> > This board is only supported by the 4.4 kernel. For that
> > reason, the preferred version is set to 4.4 and the user
> > doesn't need to specify :opt-4.4.yml
> [...]
>
> This really shouldn't be allowed to happen. All the patches applied to
> 4.4-cip to support this board were already upstream, so this must be a
> regression. If this board is used as a basis for real systems that
> need to run beyond EOL of the 4.4-cip branch (~2026), it needs to be
> possible to upgrade them to a new kernel version at that time.
Actually, the iwg20m board does work with the upstream Kernel as well as v4.19.y-cip, e.g. [1].
I think it's just that Renesas doesn't intend to support the board with anything other than v4.4.y-cip.
[1] https://lava.ciplatform.org/scheduler/job/1219
Kind regards, Chris
>
> Ben.
>
> --
> Ben Hutchings, Software Developer Codethink Ltd
> https://www.codethink.co.uk/ Dale House, 35 Dale Street
> Manchester, M1 2HF, United Kingdom
> _______________________________________________
> cip-dev mailing list
> cip-dev@lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2019-06-07 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 7:48 iwg20m with preferred kernel set to 4.4 Daniel Sangorrin
2019-06-06 7:48 ` [next] iwg20m: add support for this board Daniel Sangorrin
2019-06-06 9:09 ` Jan Kiszka
2019-06-07 14:41 ` [cip-dev] " Ben Hutchings
2019-06-07 15:06 ` Chris Paterson [this message]
2019-06-07 15:16 ` Ben Hutchings
2019-06-06 7:55 ` iwg20m with preferred kernel set to 4.4 daniel.sangorrin
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=TYAPR01MB2285605310C92322737DEB4FB7100@TYAPR01MB2285.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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