CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: quirin.gylstorff@siemens.com (Gylstorff Quirin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support
Date: Wed, 6 Nov 2019 16:53:50 +0100	[thread overview]
Message-ID: <66a2849e-bbf8-7e67-0da3-490b052f18cb@siemens.com> (raw)
In-Reply-To: <TYAPR01MB2285255EF4A6521577D5F789B7790@TYAPR01MB2285.jpnprd01.prod.outlook.com>



On 11/6/19 4:38 PM, Chris Paterson wrote:
> Hello Quirin,
> 
> Thank you for the patch.
> 
>> From: cip-dev-bounces at lists.cip-project.org <cip-dev-bounces@lists.cip-
>> project.org> On Behalf Of Q. Gylstorff
>> Sent: 06 November 2019 12:45
>>
>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>
>> The hihope-rzg2m is a ARM64 reference platform for the CIP project.
>>
>> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> ---
>>   board-rzg2m.yml                               |  16 +
>>   conf/machine/hihope-rzg2m.conf                |  17 +
>>   .../linux/files/hihope-rzg2m_defconfig        | 330 ++++++++++++++++++
>>   wic/hihope-rzg2m.wks                          |  15 +
>>   4 files changed, 378 insertions(+)
>>   create mode 100644 board-rzg2m.yml
>>   create mode 100644 conf/machine/hihope-rzg2m.conf
>>   create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
>>   create mode 100644 wic/hihope-rzg2m.wks
>>
>> diff --git a/board-rzg2m.yml b/board-rzg2m.yml
>> new file mode 100644
>> index 0000000..f68c7b8
>> --- /dev/null
>> +++ b/board-rzg2m.yml
>> @@ -0,0 +1,16 @@
>> +#
>> +# CIP Core, generic profile
>> +#
>> +# Copyright (c) Siemens AG, 2019
>> +#
>> +# Authors:
>> +#  Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> +#
>> +# SPDX-License-Identifier: MIT
>> +#
>> +
>> +header:
>> +  version: 8
>> +
>> +machine: hihope-rzg2m
>> +target: cip-core-image
>> diff --git a/conf/machine/hihope-rzg2m.conf b/conf/machine/hihope-
>> rzg2m.conf
>> new file mode 100644
>> index 0000000..5c456c7
>> --- /dev/null
>> +++ b/conf/machine/hihope-rzg2m.conf
>> @@ -0,0 +1,17 @@
>> +#
>> +# CIP Core, generic profile
>> +#
>> +# Copyright (c) Siemens AG, 2019
>> +#
>> +# Authors:
>> +#  Quirin Gylstorff <quirin.gylstorff@siemens.com>
>> +#
>> +# SPDX-License-Identifier: MIT
>> +#
>> +
>> +DISTRO_ARCH = "arm64"
>> +
>> +IMAGE_TYPE ?= "wic-img"
>> +
>> +DTB_FILE = "r8a774a1-hihope-rzg2m.dtb"
> 
> Should be r8a774a1-hihope-rzg2m-ex.dtb. The 'ex' is the sub-board that adds Ethernet/PCIe/CAN etc.

OK, I will change both occurences and post a version 2.
> 
>> +IMAGE_BOOT_FILES = "${KERNEL_IMAGE} ${DTB_FILE}"
>> diff --git a/recipes-kernel/linux/files/hihope-rzg2m_defconfig b/recipes-
>> kernel/linux/files/hihope-rzg2m_defconfig
>> new file mode 100644
>> index 0000000..f35793c
>> --- /dev/null
>> +++ b/recipes-kernel/linux/files/hihope-rzg2m_defconfig
> 
> Just to check, where did you copy this config from?

I used [0] as base.
> 
> Is there a way that the configuration could be taken directly from cip-kernel-config[0] rather than creating a copy that will need separate maintenance here?
> I ask because there is currently a merge request open[1] that will update renesas_defconfig.
> 
> [0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/blob/master/4.19.y-cip/arm64/renesas_defconfig
> [1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/merge_requests/15
> 
I will look into it using the cip-kernel-config instead of using copies 
in isar.


Quirin

  reply	other threads:[~2019-11-06 15:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 12:44 [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 1/4] kas: Increase Isar version Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 2/4] classes: add wic-targz-img.bbclass Q. Gylstorff
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support Q. Gylstorff
2019-11-06 15:38   ` Chris Paterson
2019-11-06 15:53     ` Gylstorff Quirin [this message]
2019-11-07  2:29       ` kazuhiro3.hayashi at toshiba.co.jp
2019-11-07 15:53         ` Gylstorff Quirin
2019-11-08 21:29           ` Pavel Machek
2019-11-11  6:18           ` kazuhiro3.hayashi at toshiba.co.jp
2019-11-06 12:44 ` [cip-dev] [isar-cip-core PATCH 4/4] ci: add hihope-rzg2m to ci chain Q. Gylstorff
2019-11-06 15:43   ` Chris Paterson
2019-11-07 16:39     ` [cip-dev] [isar-cip-core PATCH v2 0/4] Add rzg2m support Q. Gylstorff
2019-11-22  7:22       ` Jan Kiszka
2019-11-07 16:39     ` [cip-dev] [isar-cip-core PATCH v2 1/4] kas: Increase Isar version Q. Gylstorff
2019-11-07 16:39     ` [cip-dev] [isar-cip-core PATCH v2 2/4] classes: add wic-targz-img.bbclass Q. Gylstorff
2019-11-07 16:39     ` [cip-dev] [isar-cip-core PATCH v2 3/4] hihope-rzg2m: Add board support Q. Gylstorff
2019-11-07 16:39     ` [cip-dev] [isar-cip-core PATCH v2 4/4] ci: add hihope-rzg2m to ci chain Q. Gylstorff
2019-11-06 14:12 ` [cip-dev] [isar-cip-core PATCH 0/4] Add rzg2m support Jan Kiszka
2019-11-06 14:37   ` Gylstorff Quirin
2019-11-06 16:19     ` Chris Paterson
2019-11-08 12:57       ` Gylstorff Quirin

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=66a2849e-bbf8-7e67-0da3-490b052f18cb@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --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