From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 0/3] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels
Date: Sun, 4 Mar 2012 13:51:34 -0700 [thread overview]
Message-ID: <1330894297-4563-1-git-send-email-eric.nelson@boundarydevices.com> (raw)
In-Reply-To: <119206>
This series of patches is needed to allow main-line U-Boot to be used
with Freescale's Linux 2.6.38 non-DT kernel releases.
These releases currently require at least the machine type and
revision atag entries and are configured to load boot scripts from
the ext3 filesystem.
V2 just simplifies patch 2/3 to use CONFIG_MACH_TYPE instead of
updating mach-types.h and filling things in during boot.
Three new declarations in the board-specific header and one
new routine in the board-specific file seem like a low cost
to add a "U" (Universal) to main-line U-Boot.
Eric Nelson (3):
i.MX6: mx6q_sabrelite: add CONFIG_REVISION_TAG to allow use with
Freescale kernels
i.MX6: mx6qsabrelite: add MACH_TYPE_MX6Q_SABRELITE
i.MX6: mx6qsabrelite: add ext2 support
board/freescale/mx6qsabrelite/mx6qsabrelite.c | 7 +++++++
include/configs/mx6qsabrelite.h | 4 ++++
2 files changed, 11 insertions(+), 0 deletions(-)
In-Reply-To: http://lists.denx.de/pipermail/u-boot/2012-March/thread.html#119206
next parent reply other threads:[~2012-03-04 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <119206>
2012-03-04 20:51 ` Eric Nelson [this message]
2012-03-04 20:51 ` [U-Boot] [PATCH V2 1/3] i.MX6: mx6q_sabrelite: add CONFIG_REVISION_TAG to allow use with Freescale kernels Eric Nelson
2012-03-04 20:51 ` [U-Boot] [PATCH V2 2/3] i.MX6: mx6qsabrelite: add MACH_TYPE_MX6Q_SABRELITE Eric Nelson
2012-03-13 0:25 ` Eric Nelson
2012-03-15 8:52 ` Stefano Babic
2012-03-04 20:51 ` [U-Boot] [PATCH V2 3/3] i.MX6: mx6qsabrelite: add ext2 support Eric Nelson
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=1330894297-4563-1-git-send-email-eric.nelson@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.