public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd: set filesize variable in ubi read
Date: Tue, 12 Sep 2017 09:35:59 +0200	[thread overview]
Message-ID: <59B78E5F.10302@denx.de> (raw)
In-Reply-To: <59A7B9CE.8060902@denx.de>

Hello Holger,

Am 31.08.2017 um 09:25 schrieb Heiko Schocher:
> Hello Holger,
>
> Am 30.08.2017 um 18:38 schrieb Holger Dengler:
>> After a successful read of a UBI volume, the variable filesize is set
>> to the number of read bytes. To boot linux with a raw initramfs/initrd,
>> you must specify the exact size of the initramfs/initrd image in boot
>> command. If the initramfs/inird is read from UBI volume, $filesize is
>> required to access the number of read bytes.
>>
>> Example:
>>    ubi read ${loadaddr} kernelvol
>>    ubi read ${fdtaddr} dtbvol
>>    ubi read ${initrd_addr} initrdvol
>>    bootz ${loadaddr} ${initrd_addr}:${filesize} ${fdt_addr}
>>
>> Signed-off-by: Holger Dengler <dengler@linutronix.de>
>> ---
>>   cmd/ubi.c | 5 +++++
>>   1 file changed, 5 insertions(+)
>
> Thanks!
>
> Reviewed-by: Heiko Schocher <hs@denx.de>
>
> As new release is near, I pickup this patch when the next merge window
> opens.

Just tried a travis build, and it breaks a lot of boards, see

https://travis-ci.org/hsdenx/u-boot-ubi/builds/274457374

Do you have time to look into?

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: hs at denx.de

  reply	other threads:[~2017-09-12  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 16:38 [U-Boot] [PATCH] cmd: set filesize variable in ubi read Holger Dengler
2017-08-31  7:25 ` Heiko Schocher
2017-09-12  7:35   ` Heiko Schocher [this message]
2017-09-12  7:45     ` Holger Dengler
2017-09-12  7:58 ` [U-Boot] [PATCH v1] " Holger Dengler
2017-09-12  8:21   ` Heiko Schocher
2017-09-15  5:49   ` Heiko Schocher

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=59B78E5F.10302@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /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