From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Date: Fri, 7 Jul 2017 17:50:57 +0900 [thread overview]
Message-ID: <006f01d2f6fe$264d6c60$72e84520$@toshiba.co.jp> (raw)
Hi,
I've been working on a minimal root filesystem made with "deby".
The code is here and it includes BSP meta layers for qemux86-64, Beaglebone black,
Renesas iwg20m board and CycloneV.
https://gitlab.com/cip-playground/project-x/tree/master/deby
The meta-cip-common layer is where we put the packages that will be included
for all targets. The BSP meta-layers contain settings related to the architecture of
the processor, and Linux/u-boot configuration.
Currently, I have tested qemux86-64 and Renesas iwg20m. Both of them worked fine
so in the next step I will try to run tests on them using B at D.
# Beaglebone should work fine, but I haven't tested it yet.
For Cyclone V, I need a kernel repository.
Koguchi-san: could you create it on https://gitlab.com/cip-playground/linux-cip-cyclonev
Finally, for U-boot I need repositories to fetch the sources.
Should we have separate repositories for each board? For example:
https://gitlab.com/cip-playground/u-boot-iwg20m
https://gitlab.com/cip-playground/u-boot-cyclonev
Thanks,
Daniel
next reply other threads:[~2017-07-07 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 8:50 Daniel Sangorrin [this message]
2017-07-07 9:00 ` [cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support Chris Paterson
2017-07-07 10:40 ` Jan Kiszka
2017-07-10 23:36 ` Daniel Sangorrin
2017-07-11 6:19 ` Jan Kiszka
2017-07-11 6:34 ` Daniel Sangorrin
2017-07-11 6:42 ` Jan Kiszka
2017-07-11 7:00 ` Daniel Sangorrin
2017-07-12 9:12 ` Jan Kiszka
2017-07-13 0:12 ` Daniel Sangorrin
2017-07-13 6:37 ` Jan Kiszka
2017-07-13 7:39 ` 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='006f01d2f6fe$264d6c60$72e84520$@toshiba.co.jp' \
--to=daniel.sangorrin@toshiba.co.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox