public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Project-X (minimal root filesystem) for renesas board
Date: Thu, 29 Jun 2017 10:21:05 +0200	[thread overview]
Message-ID: <5954B871.2000601@codethink.co.uk> (raw)
In-Reply-To: <003c01d2f06f$ddc420e0$994c62a0$@toshiba.co.jp>

Hi,

On 29/06/17 02:37, Daniel Sangorrin wrote:
> Hi Koguchi-san,
>
>> -----Original Message-----
>> From: ???? / KOGUCHI?TAKUO [mailto:takuo.koguchi.sw at hitachi.com]
>> Sent: Wednesday, June 28, 2017 6:08 PM
>> To: 'Daniel Sangorrin'; cip-dev at lists.cip-project.org
>> Cc: 'Chris Paterson'
>> Subject: RE: RE: Project-X (minimal root filesystem) for renesas board
>>
>> Daniel-san,
>>
>>> I think this is not a good approach. We would need to have a new linux-cip folder for each
>>> release.
>> Let make it clear. Will you please describe your recommendation?
>
> Yes, please see below.
>
>>> Patches for the cyclone board should be on its own CIP kernel repository (where you can
>>> merge cip releases and add tags). Then, we can choose which version we want by
>>> specifying the repository and tag/commit_id.
>> Good point.  But  CIP kernel repository is curerntly used for release assuming it is tested. And CycloneV is not supported by CIP at this
>> moment. So I put the patches in the yocto project way.
>
> I didn't mean to put it on Ben's CIP repository rather on github. This way you can better maintain your "out-of-tree" cyclone V patches
> and merge (do not rebase please) changes from Ben's CIP kernel regularly. In other words, do the same as Renesas is doing at [1].
>
> [1] https://github.com/renesas-rz/renesas-cip

In order to have all the cip related code in one place, it would be 
good, if anybody is using github, that at least there is a mirror of 
that repo in gitlab. When we start automating builds/test, that would be 
helpful.

>
>>> I don't think it is necessary since the CIP root filesystem only supports a few packages.
>>> Do you mind if I rewrite this and other unnecessary definitions?
>> I am happy if you go ahead and fix it!
>
> OK, thanks. I will also separate Beaglebone from Cyclone V.
>
> Thanks,
> Daniel
>
>> Best regards,
>> Takuo Koguchi
>>
>>
>>
>>> -----Original Message-----
>>> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
>>> Sent: Wednesday, June 28, 2017 5:52 PM
>>> To: ???? / KOGUCHI?TAKUO; cip-dev at lists.cip-project.org
>>> Cc: 'Chris Paterson'
>>> Subject: [!]RE: Project-X (minimal root filesystem) for renesas board
>>>
>>> Ho Koguchi-san
>>>
>>>> -----Original Message-----
>>>> From: ???? / KOGUCHI?TAKUO [mailto:takuo.koguchi.sw at hitachi.com]
>>>> Sent: Wednesday, June 28, 2017 5:35 PM
>>>> To: Daniel Sangorrin; cip-dev at lists.cip-project.org
>>>> Cc: 'Chris Paterson'
>>>> Subject: RE: Project-X (minimal root filesystem) for renesas board
>>>>
>>>> Hi Daniel-san,
>>>>
>>>>> I have a few questions:
>>>>>    - Why do you have two directories "linux-cip" and "linux-cip2" that are almost
>>> identical?
>>>>
>>>> linux-cip directory is for linux-4.4.55-cip3.
>>>> linux-cip2 is for the previous release and it is not necessary if you update linux-cip.
>>>
>>> I think this is not a good approach. We would need to have a new linux-cip folder for each
>>> release.
>>>
>>> Patches for the cyclone board should be on its own CIP kernel repository (where you can
>>> merge cip releases and add tags). Then, we can choose which version we want by
>>> specifying the repository and tag/commit_id.
>>>
>>>>>    - I can see some xserver-related definitions on the board's
>>>>> configuration file. Are those necessary?
>>>> beaglebone.conf is based on poky/meta-yocto-bsp/conf/machine.
>>>> xserver-related definition was inculude in the original.  I am not sure if it is necessary.
>>>
>>> I don't think it is necessary since the CIP root filesystem only supports a few packages.
>>> Do you mind if I rewrite this and other unnecessary definitions?
>>>
>>> Thanks,
>>> Daniel
>>>
>>>>
>>>>
>>>> Takuo Koguchi
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
>>>>> Sent: Wednesday, June 28, 2017 4:05 PM
>>>>> To: cip-dev at lists.cip-project.org; ???? / KOGUCHI?TAKUO
>>>>> Cc: 'Chris Paterson'
>>>>> Subject: [!]Project-X (minimal root filesystem) for renesas board
>>>>>
>>>>> Hi Koguchi-san,
>>>>> Cc: Chris, cip-dev
>>>>>
>>>>> I'm going to add support to project-X for the Renesas iwg20m board
>>>>> which is equipped with an armv7 chip.
>>>>> I have noticed that you added support for beaglebone and cyclone on
>>>>> the deby-armv7 folder [1].
>>>>>
>>>>> I have a few questions:
>>>>>    - Why do you have two directories "linux-cip" and "linux-cip2" that are almost
>>> identical?
>>>>>    - I can see some xserver-related definitions on the board's
>>>>> configuration file. Are those necessary?
>>>>>
>>>>> Thanks,
>>>>> Daniel
>>>>>
>>>>> [1]
>>>>> https://gitlab.com/cip-playground/project-x/tree/master/deby-armv7
>>>>>
>>>
>>>
>
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

  reply	other threads:[~2017-06-29  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  7:04 [cip-dev] Project-X (minimal root filesystem) for renesas board Daniel Sangorrin
2017-06-28  8:35 ` 小口琢夫 / KOGUCHI,TAKUO
2017-06-28  8:51   ` Daniel Sangorrin
2017-06-28  9:07     ` 小口琢夫 / KOGUCHI,TAKUO
2017-06-29  0:37       ` Daniel Sangorrin
2017-06-29  8:21         ` Agustin Benito Bethencourt [this message]
2017-07-07  2:40           ` Daniel Sangorrin
2017-07-07  8:54             ` Agustin Benito Bethencourt
2017-07-07 13:16               ` KOBAYASHI Yoshitake
2017-08-03 13:18             ` Chris Paterson
2017-08-04  7:18               ` 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=5954B871.2000601@codethink.co.uk \
    --to=agustin.benito@codethink.co.uk \
    --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