public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: <daniel.sangorrin@toshiba.co.jp>
To: <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 08:17:57 +0000	[thread overview]
Message-ID: <TY2PR01MB332378867EA4864E50DF494AD0170@TY2PR01MB3323.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <0b70c8f4-9ca2-1ef6-d1a3-826dc71d5a96@siemens.com>

> Does the pre-installed u-boot support ext4? 

ext4load seems to be available on the u-boot command line.

>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).

> That would avoid duplicating information
> like partitioning and kernel parameters here.

I guess, I can just load the image with ext4load instead of fatload. Not sure why the original instructions required two partitions then..

Thanks,
Daniel


  reply	other threads:[~2019-06-06  8:18 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 [this message]
2019-06-06  8:26         ` Claudius Heine

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=TY2PR01MB332378867EA4864E50DF494AD0170@TY2PR01MB3323.jpnprd01.prod.outlook.com \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    --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