All of lore.kernel.org
 help / color / mirror / Atom feed
From: kazuhiro3.hayashi@toshiba.co.jp (kazuhiro3.hayashi at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support
Date: Mon, 11 Nov 2019 06:18:31 +0000	[thread overview]
Message-ID: <TYAPR01MB42866037FF77023DC54A373EE1740@TYAPR01MB4286.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <d41024b8-0d3f-a4e6-fef3-76dc350dfc62@siemens.com>

Hello Quirin,

> On 11/7/19 3:29 AM, kazuhiro3.hayashi at toshiba.co.jp wrote:
> > Hello Quirin,
> >
> >> I will look into it using the cip-kernel-config instead of using copies
> >> in isar.
> >
> > Are you planning to "fetch" required config(s) for each target from cip-kernel-config?
> > or, keep copies of the configs in isar-cip-core then synchronize them at the specific point?
> 
> I try to fetch the configuration for each target from cip-kernel-config.

Thanks!
As the first step, I will do the same way in deby to use existing configs in cip-kernel-config.

Best regards,
Kazu

> Currently I need to patch the config as Isar doesn't allow setting
> CONFIG_LOCALVERSION in the kernel configuration.
> 
> >
> > Deby also has its own kernel configs (arm64 defconfig + Tiny hihope-rzg2m.config)
> > for HiHope RZG2M:
> >
> https://gitlab.com/cip-project/cip-core/deby/blob/cip-core-buster/meta-hihope-rzg2m/recipes-kernel/linux/linux-ba
> se_git.bbappend
> > but they also should be replaced by the common kernel configs in CIP.
> > As the first step, I would provide configs by the same way as isar-cip-core.
> >
> > Best regards,
> > Kazu
> >
> >
> 
> Quirin

  parent reply	other threads:[~2019-11-11  6:18 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
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 [this message]
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=TYAPR01MB42866037FF77023DC54A373EE1740@TYAPR01MB4286.jpnprd01.prod.outlook.com \
    --to=kazuhiro3.hayashi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.