From: Claudius Heine <ch@denx.de>
To: daniel.sangorrin@toshiba.co.jp, jan.kiszka@siemens.com,
cip-dev@lists.cip-project.org
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] iwg20m: add support for this board
Date: Thu, 6 Jun 2019 10:26:46 +0200 [thread overview]
Message-ID: <1319553a-38d0-a4f1-0590-7c6f71d9fbd2@denx.de> (raw)
In-Reply-To: <TY2PR01MB332378867EA4864E50DF494AD0170@TY2PR01MB3323.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1195 bytes --]
Hi,
On 06/06/2019 10.17, daniel.sangorrin@toshiba.co.jp wrote:
>> If yes, why not using u-boot-script
>> and loading /boot/boot.scr instead?
>
> After loading boot.scr, don't we need the "source" command to work? "source" does not seem to be configured in the pre-installed u-boot.
>
> Also, to create boot.scr we need mkimage. I wonder if modern Debian u-boot-tools' mkimage will create a boot.scr that is compatible with the pre-installed u-boot (remember that I couldn't build the old u-boot with the new compilers).
You could just use the mkimage that comes from your u-boot source to be
certain. I do something similar [1] since the upstream debian
u-boot-tools do not support creating signed fit images.
[1] https://github.com/ilbers/isar/blob/master/meta/classes/fit-img.bbclass
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-06-06 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Add support for iwg20m to ISAR CIP Core>
2019-06-06 2:02 ` Daniel Sangorrin
2019-06-06 2:02 ` [PATCH] iwg20m: add support for this board Daniel Sangorrin
2019-06-06 6:20 ` Jan Kiszka
2019-06-06 8:17 ` daniel.sangorrin
2019-06-06 8:26 ` Claudius Heine [this message]
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=1319553a-38d0-a4f1-0590-7c6f71d9fbd2@denx.de \
--to=ch@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.sangorrin@toshiba.co.jp \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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