public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D: iwg20m support
Date: Thu, 29 Mar 2018 08:23:21 +0900	[thread overview]
Message-ID: <003201d3c6eb$c2d9e370$488daa50$@toshiba.co.jp> (raw)
In-Reply-To: <6afbe7517b484b508ce366d33c2e9c12@rvc.renesas.com>

Thanks for the feedback Tram.
I will set the cortexa15hf tuning as default.

Thanks,
Daniel

> -----Original Message-----
> From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> Sent: Wednesday, March 28, 2018 8:19 PM
> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org; Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>;
> O365-Minh Thuy Dinh. Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu <chan.vu.xv@renesas.com>
> Subject: RE: [cip-dev] B at D: iwg20m support
> 
> Hi Daniel,
> 
> I'm sorry for late reply.
> After rebuilding cip core with cortexa15hf tuning, I can run binary files successfully.
> 
> Thank you and best regards,
> Tram Nguyen
> 
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Monday, March 26, 2018 3:59 PM
> To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S' <zoran.stojsavljevic.de@gmail.com>
> Cc: O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org; Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>;
> O365-Minh Thuy Dinh. Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu <chan.vu.xv@renesas.com>
> Subject: RE: [cip-dev] B at D: iwg20m support
> 
> Hi Tram,
> 
> > -----Original Message-----
> > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > Sent: Monday, March 26, 2018 5:54 PM
> > To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; 'Zoran S'
> > <zoran.stojsavljevic.de@gmail.com>
> > Cc: O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi
> > <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> > <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org; Binh
> > Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; O365-Minh Thuy Dinh.
> > Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu
> > <chan.vu.xv@renesas.com>
> > Subject: RE: [cip-dev] B at D: iwg20m support
> >
> > Hi Daniel,
> >
> > I got it. Thank you for your information.
> > Our SDK information: "cortexa15hf"
> 
> If you want you can rebuild cip core with cortexa15hf tuning.
> 
> $ vi conf/machine/iwg20m.conf
> DEFAULTTUNE ?= cortexa15hf
> 
> Then you _may_ be able to use your SDK as it is.
> 
> Maybe I will set it as default.
> 
> Best regards
> Daniel
> 
> >
> > Best regards,
> > Tram Nguyen
> >
> > -----Original Message-----
> > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> > Sent: Monday, March 26, 2018 3:45 PM
> > To: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>; 'Zoran S'
> > <zoran.stojsavljevic.de@gmail.com>
> > Cc: O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi
> > <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> > <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org; Binh
> > Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; O365-Minh Thuy Dinh.
> > Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu
> > <chan.vu.xv@renesas.com>
> > Subject: RE: [cip-dev] B at D: iwg20m support
> >
> > Hi Tram,
> >
> > > -----Original Message-----
> > > From: Tram Quynh Thi. Nguyen [mailto:tram.nguyen.xw at rvc.renesas.com]
> > > Sent: Monday, March 26, 2018 5:40 PM
> > > To: Zoran S <zoran.stojsavljevic.de@gmail.com>; Daniel Sangorrin
> > > <daniel.sangorrin@toshiba.co.jp>
> > > Cc: O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi
> > > Onishi <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> > > <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip-project.org;
> > > Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; O365-Minh Thuy Dinh.
> > > Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu
> > > <chan.vu.xv@renesas.com>
> > > Subject: RE: [cip-dev] B at D: iwg20m support
> > >
> > > Hi Daniel,
> > >
> > > Thank you for your support.
> > >
> > > Hi Zoran,
> > >
> > > Thank you for your support.
> > >
> > > I followed this guide to build for Renesas iwg20m board and got the results without errors:
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > > ip
> > > -iwg20m/README.IWG20M.txt
> > >
> > > Daniel got my idea.
> > > In our environment, we use different SDK to compile c source to binary.
> > > That a reason why I asked for SDK.
> >
> > If you are allowed, could you give me some information about your SDK?
> > For example, the one in CIP core uses the "cortexa15" tuning, but yours maybe using "cortexa15hf" for example.
> >
> > Also, if your tests are using dynamic linking then you need to make
> > sure that your SDK library headers are the same version as the libraries on the target as well. If you use static linking I think it should
> not matter.
> >
> > Thanks,
> > Daniel
> >
> > > -----Original Message-----
> > > From: Zoran S [mailto:zoran.stojsavljevic.de at gmail.com]
> > > Sent: Monday, March 26, 2018 2:55 PM
> > > To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> > > Cc: Tram Quynh Thi. Nguyen <tram.nguyen.xw@rvc.renesas.com>;
> > > O365-Anh The. Tran <anh.tran.jc@renesas.com>; O365-Yasushi Onishi
> > > <yasushi.onishi.xc@renesas.com>; O365-Yoshinori Kaneko
> > > <yoshinori.kaneko.xg@renesas.com>; cip-dev at lists.cip- project.org;
> > > Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; O365-Minh Thuy
> > > Dinh. Tran <minh.tran.xc@renesas.com>; O365-Chan Duc. Vu
> > > <chan.vu.xv@renesas.com>
> > > Subject: Re: [cip-dev] B at D: iwg20m support
> > >
> > > Hello Tram,
> > >
> > > I have no idea what you are talking here (which problem with
> > > iwg20m), but if you (as Daniel mentioned) are dealing with YOCTO
> > > build, I finally (after in total 3 days of struggle) built one on
> > > Saturday (on my home network). I am just about (today) to test out
> > > of CIP
> > YOCTO kernel 4.4.-x, initramfs.gpio.gz and .dtb.
> > >
> > > It has nothing to do with Daniel's Sangorrin kas script (which is
> > > based upon configuration tool called kas - Siemens based - authors Jan Kiszka, Daniel Wagner and Henning Schill):
> > > Kas iwg20d script is here:
> > > https://gitlab.com/cip-project/cip-core/blob/master/deby/poky/meta-c
> > > ip
> > > -bbb/kas-bbb.yml
> > > .
> > >
> > > I was NOT able to build it, due to the following error:
> > > https://www.mail-archive.com/yocto at yoctoproject.org/msg39512.html
> > >
> > > Rather, my YOCTO build has everything to do with:
> > > https://elinux.org/RZ-G/Boards/Yocto_2.0
> > >
> > > I compiled it... And have created loads for core-image-minimal and
> > > core-image-weston (weston is Wayland compositor, behind Wayland server protocol).
> > >
> > > It is a bit peculiar environment required to build the outdated
> > > YOCTO... ;-)
> > >
> > > Zoran
> > > _______
> > >
> > > On Mon, Mar 26, 2018 at 3:08 AM, Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp> wrote:
> > > > Dear Tram,
> > > >
> > > >> -----Original Message-----
> > > >> From: Tram Quynh Thi. Nguyen
> > > >> [mailto:tram.nguyen.xw at rvc.renesas.com]
> > > >> Sent: Friday, March 23, 2018 11:34 PM
> > > >> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> > > >> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu
> > > >> <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran
> > > >> <minh.tran.xc@renesas.com>; O365-Anh The. Tran
> > > >> <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen
> > > >> <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko
> > > >> <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi
> > > >> <yasushi.onishi.xc@renesas.com>
> > > >> Subject: RE: [cip-dev] B at D: iwg20m support
> > > >>
> > > >> Dear Daniel-san,
> > > >> CC all,
> > > >>
> > > >> Currently, I found below issue when running Test Cases on your environment or newest cip-core environment:
> > > >> - Cannot run any binary files.
> > > >> Reason: We use our SDK to build the binary files.
> > > >>
> > > >> Could you please share how to compile binary to run on this envionment?
> > > >> Thank you for your support.
> > > >
> > > > To build the SDK use "bitbake meta-toolchain".
> > > >
> > > > Thanks,
> > > > Daniel
> > > >
> > > >> -----Original Message-----
> > > >> From: Trung. Huynh
> > > >> Sent: Friday, January 12, 2018 9:16 AM
> > > >> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> > > >> Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu
> > > >> <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran
> > > >> <minh.tran.xc@renesas.com>; O365-Anh The. Tran
> > > >> <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen
> > > >> <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko
> > > >> <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi
> > > >> <yasushi.onishi.xc@renesas.com>; Tram Quynh Thi. Nguyen
> > > >> <tram.nguyen.xw@rvc.renesas.com>
> > > >> Subject: RE: [cip-dev] B at D: iwg20m support
> > > >>
> > > >> Dear Daniel
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> > > >> > Sent: Thursday, January 11, 2018 12:50 PM
> > > >> > To: Trung. Huynh <trung.huynh.uw@rvc.renesas.com>
> > > >> > Cc: cip-dev at lists.cip-project.org; O365-Chan Duc. Vu
> > > >> > <chan.vu.xv@renesas.com>; O365-Minh Thuy Dinh. Tran
> > > >> > <minh.tran.xc@renesas.com>; O365-Anh The. Tran
> > > >> > <anh.tran.jc@renesas.com>; Binh Thanh. Nguyen
> > > >> > <binh.nguyen.uw@rvc.renesas.com>; O365-Yoshinori Kaneko
> > > >> > <yoshinori.kaneko.xg@renesas.com>; O365-Yasushi Onishi
> > > >> > <yasushi.onishi.xc@renesas.com>
> > > >> > Subject: RE: [cip-dev] B at D: iwg20m support
> > > >> >
> > > >> > 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?
> > > >>
> > > >> Is v4.4.55-cip3 the "Jethro" one? Because I saw this is the build I was use.
> > > >>
> > > >> >
> > > >> > I have added your kernel configuration changes:
> > > >> > https://gitlab.com/cip-project/cip-core/commit/c1efa63259098157
> > > >> > 31
> > > >> > ab
> > > >> > e0b
> > > >> > 69ec7e19e2e56aee7 Please let me know if that works for you.
> > > >>
> > > >> Anyway, let get back to master branch with flags from your suggestion, the issue seems get to worse than previous one:
> > > >> After uboot pull necessary packages on RAM up, it get stuck at:
> > > >>
> > > >> Starting kernel ...
> > > >>
> > > >> Nothing print out after this, so we didn't explore what occurring
> > > >> I also tried to test with v4.4.83-cip8 if any possibility to
> > > >> solve the problem but same things
> > > >>
> > > >> >
> > > >> > 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?
> > > >>
> > > >> In circle development process, we build up our target packages by
> > > >> Yocto But for this cip-core testing with B at D, I'm using the compiler which to be installed via Ubuntu's repository:
> > > >> gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1)
> > > >>
> > > >> >
> > > >> > 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.
> > > >> > > > > > > > > or
> > > >> > > > > > > > > g/ci
> > > >> > > > > > > > > p- co re
> > > >> > > > > > > > > /iwg20m/core-image-minimal-iwg20m.cpio.gz
> > > >> > > > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.
> > > >> > > > > > > > > or
> > > >> > > > > > > > > g/ci
> > > >> > > > > > > > > p-
> > > >> > > > > > > > > co
> > > >> > > > > > > > > re
> > > >> > > > > > > > > /iwg20m/r8a7743-iwg20d-q7.dtb
> > > >> > > > > > > > > https://s3-us-west-2.amazonaws.com/download.cip-project.
> > > >> > > > > > > > > or
> > > >> > > > > > > > > g/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/doc
> > > >> > > > > > > > s/
> > > >> > > > > > > > ka
> > > >> > > > > > > > s-b
> > > >> > > > > > > > bb
> > > >> > > > > > > > .yml
> > > >> > > > > > > > https://github.com/igaw/cip-rt-misc/blob/master/doc
> > > >> > > > > > > > s/
> > > >> > > > > > > > ka
> > > >> > > > > > > > s-m
> > > >> > > > > > > > in
> > > >> > > > > > > > nowb
> > > >> > > > > > > > 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/civilinfrastructurep
> > > >> > > > > > > la
> > > >> > > > > > > tf
> > > >> > > > > > > orm
> > > >> > > > > > > /c
> > > >> > > > > > > ip-c
> > > >> > > > > > > or
> > > >> > > > > > > e-
> > > >> > > > > > > quickstart
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -iwg20m/README.IWG20M.txt
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -iwg20m/kas-iwg20m.yml
> > > >> > > > > > >
> > > >> > > > > > > An overview of the CIP Core is here:
> > > >> > > > > > > https://wiki.linuxfoundation.org/civilinfrastructurep
> > > >> > > > > > > la
> > > >> > > > > > > tf
> > > >> > > > > > > orm
> > > >> > > > > > > /c
> > > >> > > > > > > ip-c
> > > >> > > > > > > or e
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > REA
> > > >> > > > > > > DM
> > > >> > > > > > > E.md
> > > >> > > > > > >
> > > >> > > > > > > For the BBB please check this other Readme and kas file:
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > meta
> > > >> > > > > > > -c
> > > >> > > > > > > ip
> > > >> > > > > > > -bbb/README.BBB.txt
> > > >> > > > > > > https://gitlab.com/cip-project/cip-core/blob/master/d
> > > >> > > > > > > eb
> > > >> > > > > > > y/
> > > >> > > > > > > pok
> > > >> > > > > > > y/
> > > >> > > > > > > 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-de
> > > >> > > > > > > v
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >
> > > >
> > > > _______________________________________________
> > > > cip-dev mailing list
> > > > cip-dev at lists.cip-project.org
> > > > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
> 
> 

  parent reply	other threads:[~2018-03-28 23:23 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
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 [this message]
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='003201d3c6eb$c2d9e370$488daa50$@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