public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
	cip-dev@lists.cip-project.org, isar-users@googlegroups.com
Subject: Re: porting iwg20m to isar-cip-core
Date: Wed, 5 Jun 2019 08:00:26 +0200	[thread overview]
Message-ID: <d0acd9f6-2f30-2407-c202-5600b3750352@siemens.com> (raw)
In-Reply-To: <20190605021645.4464-1-daniel.sangorrin@toshiba.co.jp>

On 05.06.19 04:16, Daniel Sangorrin wrote:
> I wanted to use uImage because that's what is used in the
> iwg20m manual, and it's known to work on Deby as well.
> Ref: https://gitlab.com/cip-project/cip-core/deby/blob/master/poky/meta-cip-iwg20m/README.IWG20M.txt
> Do you suggest that we should use bootz instead of bootm?
> Is uImage not recommended or something? I have used uImage in many boards.

BTW, we chose bootz (and distro boot) in order to be able to boot also stock 
Debian kernels - which work on a (slowly) increasing number of boards. I.e. Isar 
is modeled around the ideal case, not legacy ones.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2019-06-05  6:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  2:16 Daniel Sangorrin
2019-06-05  2:16 ` [isar-cip-core] iwg20m: temporary patch for review v2 Daniel Sangorrin
2019-06-07 14:55   ` [cip-dev] " Ben Hutchings
2019-06-05  5:34 ` porting iwg20m to isar-cip-core daniel.sangorrin
2019-06-05  5:51   ` Jan Kiszka
2019-06-05  6:00 ` Jan Kiszka [this message]
2019-06-05  8:27   ` 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=d0acd9f6-2f30-2407-c202-5600b3750352@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=isar-users@googlegroups.com \
    /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