From: brendan <brendan.ta@jacques.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to validate ext4load file size (not null)?
Date: Thu, 23 Feb 2017 17:58:15 -0700 (MST) [thread overview]
Message-ID: <1487897895174-282781.post@n7.nabble.com> (raw)
I have stored multiple device trees in my emmc (ext4 formatted) partition and
I want to load a certain device tree file from emmc, but if this fails (i.e.
the device tree file doesn't exist) it should default to a device tree that
is stored in memory.
For example if I run this:
I get a return of:
Is there a way I can parse this return from ext4load to check if the size is
null or not null?
The aim (in pseudo code) is
Does uBoot offer functionality for what I am after? or should I be
approaching it with a different method.
Thanks
--
View this message in context: http://u-boot.10912.n7.nabble.com/How-to-validate-ext4load-file-size-not-null-tp282781.html
Sent from the U-Boot mailing list archive at Nabble.com.
next reply other threads:[~2017-02-24 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 0:58 brendan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-24 2:03 [U-Boot] How to validate ext4load file size (not null)? brendan
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=1487897895174-282781.post@n7.nabble.com \
--to=brendan.ta@jacques.com.au \
--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