From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D: iwg20m support
Date: Thu, 11 Jan 2018 14:49:48 +0900 [thread overview]
Message-ID: <008f01d38a9f$fdce8680$f96b9380$@toshiba.co.jp> (raw)
In-Reply-To: <bacb02dc0d194be8b13138e98cf8aa33@rvc.renesas.com>
Dear Trung san,
> -----Original Message-----
> From: Trung. Huynh [mailto:trung.huynh.uw at rvc.renesas.com]
..
> >
> > Please let me confirm just in case. Am I right if I say that you plan to you submit not only the kernel configuration flags
> > but also test dependency definitions to cip core, and the corresponding yaml files for B at D?.
> > If that's correct I will be glad to accept them.
>
> Yes, we would love to be apart in B at D with our contribution for who need to take our test suites as a testing plan.
> We do not promise this is to become excellent suites but we do our best to have a good things that somebody to
> think about at first
OK, that's great!
> > > Regarding shmobile_defconfig, attachment shows up for you.
> >
> > Thanks, you only changed these flags right?
> > CONFIG_BLK_DEV_RAM_SIZE=250000
> > CONFIG_BLK_DEV_RAM_COUNT=4
>
> You're right, the cip-core I pulled down from global site without changing anything, it just be changed those flags
> and built under standalone of Linaro's cross compiler.
I just realized that you might be using the wrong branch of cip-core. You should be using the "master" branch not the "jethro"
one which was used and frozen for the cip-core release and the quickstart wiki page (the master branch depends on "morty").
The jethro branch was using a non-official CIP kernel repository (https://github.com/renesas-rz/renesas-cip) but on the
master branch we are using the official CIP kernel. For that reason, shmobile_defconfig on the main branch is different
and some drivers have not been merged yet.
Please could you check which branch you are using?
I have added your kernel configuration changes:
https://gitlab.com/cip-project/cip-core/commit/c1efa6325909815731abe0b69ec7e19e2e56aee7
Please let me know if that works for you.
Could you show me how you built cip-core using Linaro's cross compiler?
By the way, cip-core builds its own toolchain, are you using Linaro's to reduce build time?
Thanks,
Daniel
> > > > > -----Original Message-----
> > > > > From: cip-dev-bounces at lists.cip-project.org
> > > > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Daniel
> > > > > Sangorrin
> > > > > Sent: Tuesday, December 19, 2017 8:40 AM
> > > > > To: 'Daniel Wagner' <daniel.wagner@siemens.com>
> > > > > Cc: cip-dev at lists.cip-project.org
> > > > > Subject: Re: [cip-dev] B at D: iwg20m support
> > > > >
> > > > > Dear Daniel Wagner,
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Daniel Wagner [mailto:daniel.wagner at siemens.com]
> > > > > > Sent: Monday, December 18, 2017 8:36 PM
> > > > > > To: Daniel Sangorrin
> > > > > > Cc: cip-dev at lists.cip-project.org
> > > > > Subject: Re: [cip-dev] B at D: iwg20m support
> > > > > >
> > > > > > Hi Daniel,
> > > > > >
> > > > > > On 12/14/2017 06:57 AM, Daniel Sangorrin wrote:
> > > > > > > Hi Trung-san, Robert and all
> > > > > > >
> > > > > > > I received the AWS credentials from Agustin and uploaded the
> > > > > > > cip-core binaries for the Renesas iwg20m board.
> > > > > > >
> > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/ci
> > > > > > > p- co re /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/ci
> > > > > > > p-
> > > > > > > co
> > > > > > > re
> > > > > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.org/ci
> > > > > > > p-
> > > > > > > co
> > > > > > > re
> > > > > > > /iwg20m/uImage
> > > > > >
> > > > > > Just out of curiosity: how did you build the root fs? The naming
> > > > > > indicates that you used Yocto. I am still setting up my test
> > > > > > environment for rt testing and wrote two kas files to create me a root fs:
> > > > > >
> > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-bbb.yml
> > > > > > https://github.com/igaw/cip-rt-misc/blob/master/docs/kas-minnowb
> > > > > > oa
> > > > > > rd
> > > > > > .y
> > > > > > ml
> > > > > >
> > > > > > They are not self contained yet. Will fixed that right now. The
> > > > > > idea that you can write
> > > > > >
> > > > > > kas build kas-bbb.yml
> > > > > >
> > > > > > and you get a root fs for testing.
> > > > >
> > > > > The CIP Core rootfs was built using Deby (poky build system +
> > > > > meta-debian). You can see a tutorial in the CIP wiki and a more up-to- date README and kas file in the source code.
> > > > >
> > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-c
> > > > > or
> > > > > e-
> > > > > quickstart
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -iwg20m/README.IWG20M.txt
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -iwg20m/kas-iwg20m.yml
> > > > >
> > > > > An overview of the CIP Core is here:
> > > > > https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-c
> > > > > or e
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/README.md
> > > > >
> > > > > For the BBB please check this other Readme and kas file:
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -bbb/README.BBB.txt
> > > > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta
> > > > > -c
> > > > > ip
> > > > > -bbb/kas-bbb.yml
> > > > >
> > > > > You can add the packages "openssh nfs-utils rt-tests strace procps", they are available in meta-debian.
> > > > >
> > > > > Unfortunately, you cannot simply add "meta-qt5" because it may
> > > > > conflict with meta-debian. Instead you would need to use meta- debian qt5 recipes (only if you really need qt5 for testing RT).
> > > > >
> > > > > Thanks,
> > > > > Daniel Sangorrin
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > cip-dev mailing list
> > > > > cip-dev at lists.cip-project.org
> > > > > https://lists.cip-project.org/mailman/listinfo/cip-dev
> > > >
> > > >
> > >
> > >
>
>
next prev parent reply other threads:[~2018-01-11 5:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 5:57 [cip-dev] B@D: iwg20m support Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 1/3] Vagrantfile: support the http proxy plugin Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 2/3] iwg20m: add device type and dictionary template Daniel Sangorrin
2017-12-14 6:06 ` Daniel Sangorrin
2017-12-14 5:57 ` [cip-dev] [PATCH 3/3] iwg20m: add a test that boots a cip-core ramdisk Daniel Sangorrin
2017-12-18 11:36 ` [cip-dev] B@D: iwg20m support Daniel Wagner
2017-12-19 1:40 ` Daniel Sangorrin
2018-01-02 9:37 ` Trung. Huynh
2018-01-09 8:40 ` Daniel Sangorrin
2018-01-09 10:40 ` Trung. Huynh
2018-01-09 23:55 ` Daniel Sangorrin
2018-01-10 4:04 ` Trung. Huynh
2018-01-10 5:25 ` Daniel Sangorrin
2018-01-10 6:58 ` Trung. Huynh
2018-01-11 5:49 ` Daniel Sangorrin [this message]
2018-01-12 2:16 ` Trung. Huynh
2018-03-23 14:34 ` Tram Quynh Thi. Nguyen
2018-03-26 1:08 ` Daniel Sangorrin
2018-03-26 7:54 ` Zoran S
2018-03-26 8:39 ` Tram Quynh Thi. Nguyen
2018-03-26 8:45 ` Daniel Sangorrin
2018-03-26 8:53 ` Tram Quynh Thi. Nguyen
2018-03-26 8:59 ` Daniel Sangorrin
2018-03-28 11:19 ` Tram Quynh Thi. Nguyen
2018-03-28 11:52 ` Zoran S
2018-03-29 3:37 ` Tram Quynh Thi. Nguyen
2018-03-29 8:23 ` Zoran S
2018-03-28 23:23 ` Daniel Sangorrin
2018-01-02 9:45 ` [cip-dev] FW: " Trung. Huynh
2018-01-02 11:26 ` [cip-dev] " Daniel Wagner
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='008f01d38a9f$fdce8680$f96b9380$@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