From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 2/2] ARM: omap3: evm: Fix distro bootcmd UBIFS and MMC support
Date: Sun, 28 Jan 2018 13:53:44 -0500 [thread overview]
Message-ID: <20180128185344.GQ20149@bill-the-cat> (raw)
In-Reply-To: <20180121031614.29091-3-woods.technical@gmail.com>
On Sat, Jan 20, 2018 at 09:16:14PM -0600, Derald D. Woods wrote:
> The omap3_evm board does not boot when commit:
> a47ca2cf67 ("ARM: omap3: evm: Add kernel image loading from UBIFS and EXT4")
> is applied after commit:
> 3dde8f2037 ("Merge git://git.denx.de/u-boot-mmc")
>
> This commit reduces the CONFIG_EXTRA_ENV_SETTINGS size and better
> leverages the existing distro bootcmd infrastructure.
>
> - Use updated UBIFS support from config_distro_bootcmd.h
> - Use LEGACY_MMC naming found in am335x_evm.h and ti_omap4_common.h
> - Remove extra environment content that is no longer needed
>
> [MMC(0:1)/extlinux/extlinux.conf]
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180128/668b4f1c/attachment.sig>
prev parent reply other threads:[~2018-01-28 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 3:16 [U-Boot] [PATCH 0/2] ARM: omap3: evm: Fix distro bootcmd Derald D. Woods
2018-01-21 3:16 ` [U-Boot] [PATCH 1/2] distro bootcmd: Allow board defined UBI partition and volume names Derald D. Woods
2018-01-28 18:53 ` [U-Boot] [U-Boot, " Tom Rini
2018-01-21 3:16 ` [U-Boot] [PATCH 2/2] ARM: omap3: evm: Fix distro bootcmd UBIFS and MMC support Derald D. Woods
2018-01-28 18:53 ` Tom Rini [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=20180128185344.GQ20149@bill-the-cat \
--to=trini@konsulko.com \
--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