From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Request for guidance: removal of old config files [was: Kernel configurations for 4.19?]
Date: Sun, 21 Jul 2019 18:25:59 +0200 [thread overview]
Message-ID: <20190721162559.GB10770@amd> (raw)
In-Reply-To: <fae9b423882c15f5e31eaef237086f38055dcfce.camel@codethink.co.uk>
On Fri 2019-07-12 17:34:47, Ben Hutchings wrote:
> On Thu, 2019-07-11 at 18:51 +0200, Jan Kiszka wrote:
> [...]
> > > 4.19/arm/hitachi_omap_defconfig
> > > 4.19/arm/moxa_mxc_defconfig
> > > 4.19/arm/siemens_am335x-axm2_defconfig
> > > 4.19/arm/siemens_am335x-draco_defconfig
> > > 4.19/arm/siemens_am335x-dxr2_defconfig
> > > 4.19/arm/siemens_am335x-etamin_defconfig
> > > 4.19/arm/siemens_am57xx-pxm3_defconfig
> >
> > Those can go, I'm not aware of their usage on 4.19. But do we have one for the
> > am335-x-based BBB, our reference board?
>
> Good point. I have not yet tried running 4.19 on the BBB, but I can
> look at adding one - or perhaps Nobuhiro or Pavel already has a
> suitable config?
No easy access to BBB here, sorry.
I have added directory 4.19-rt and added config for socfpga I'd like
to be used for testing in Lava lab. It is not configuration that needs
to be officially supported with CIP project.
I hope that is okay.
If someone uses rt on some other hardware, I'd like to know.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190721/d06d99d0/attachment.sig>
next prev parent reply other threads:[~2019-07-21 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 11:53 [cip-dev] Kernel configurations for 4.19? Ben Hutchings
2019-04-19 6:03 ` daniel.sangorrin at toshiba.co.jp
2019-05-22 8:57 ` daniel.sangorrin at toshiba.co.jp
2019-05-09 10:11 ` Chris Paterson
2019-06-12 0:12 ` Masato Minda
2019-06-16 21:49 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-09 13:49 ` Ben Hutchings
2019-07-09 14:40 ` Ben Hutchings
2019-07-12 0:57 ` daniel.sangorrin at toshiba.co.jp
[not found] ` <7c8d175eaa43357d6484c6fee89c4d0f@codethink.co.uk>
[not found] ` <909b4353-87c9-08e2-46f1-4ef8ce3fb6d2@siemens.com>
2019-07-12 16:34 ` [cip-dev] Request for guidance: removal of old config files [was: Kernel configurations for 4.19?] Ben Hutchings
2019-07-14 22:42 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-21 16:25 ` Pavel Machek [this message]
2019-07-21 17:58 ` Zoran S
2019-07-21 18:28 ` Pavel Machek
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=20190721162559.GB10770@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.