From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 2/3] ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layout
Date: Wed, 14 Mar 2018 10:09:59 -0400 [thread overview]
Message-ID: <20180314140959.GY1770@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <20180226235259.21413-3-woods.technical@gmail.com>
On Mon, Feb 26, 2018 at 05:52:58PM -0600, Derald D. Woods wrote:
> This commit does the following for BeagleBoard{-xM}:
>
> - Enable DM_SERIAL which also enables SPL_DM_SERIAL
> - Misc. config updates in support of DM_SERIAL
> - Use updated NAND layout (BeagleBoard):
>
> device nand0 <omap2-nand.0>, # parts = 6
>
> #: name size offset
> -------------------------------------------------
> 0: spl 0x00080000(512k) 0x00000000
> 1: u-boot 0x001e0000(1920k) 0x00080000
> 2: u-boot-env 0x00020000(128k) 0x00260000
> 3: dtb 0x00020000(128k) 0x00280000
> 4: kernel 0x00600000(6m) 0x002a0000
> 5: rootfs 0x0f760000(-) 0x008a0000
> -------------------------------------------------
>
> - Use MMC and UBIFS support from config_distro_bootcmd.h
> - Use LEGACY_MMC and NAND support defined in omap3_beagle.h
>
> [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/20180314/c2155918/attachment.sig>
next prev parent reply other threads:[~2018-03-14 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 5:13 [U-Boot] [RFC PATCH 0/3] ARM: omap3: beagle, evm: synchronize common setup Derald D. Woods
2018-02-12 5:13 ` [U-Boot] [RFC PATCH 1/3] ARM: omap3: beagle: Set 'mtdids' and 'mtdparts' in board file Derald D. Woods
2018-02-12 5:13 ` [U-Boot] [RFC PATCH 2/3] ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layout Derald D. Woods
2018-02-12 5:13 ` [U-Boot] [RFC PATCH 3/3] ARM: omap3: evm: Sync with omap3_beagle configuration Derald D. Woods
2018-02-24 14:09 ` [U-Boot] [PATCH v2 0/3] ARM: omap3: beagle, evm: synchronize common setup Derald D. Woods
2018-02-24 14:09 ` [U-Boot] [PATCH v2 1/3] ARM: omap3: beagle: Set 'mtdids' and 'mtdparts' in board file Derald D. Woods
2018-02-24 14:09 ` [U-Boot] [PATCH v2 2/3] ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layout Derald D. Woods
2018-02-24 14:09 ` [U-Boot] [PATCH v2 3/3] ARM: omap3: evm: Sync with omap3_beagle configuration Derald D. Woods
2018-02-24 14:35 ` [U-Boot] [PATCH v2 0/3] ARM: omap3: beagle, evm: synchronize common setup Tom Rini
2018-02-24 15:29 ` Derald D. Woods
2018-02-24 19:12 ` Tom Rini
2018-02-24 19:39 ` Derald Woods
2018-02-24 20:02 ` Tom Rini
2018-02-25 18:54 ` Derald D. Woods
2018-02-26 23:52 ` [U-Boot] [PATCH v3 " Derald D. Woods
2018-02-26 23:52 ` [U-Boot] [PATCH v3 1/3] ARM: omap3: beagle: Set 'mtdids' and 'mtdparts' in board file Derald D. Woods
2018-03-14 14:09 ` [U-Boot] [U-Boot, v3, " Tom Rini
2018-02-26 23:52 ` [U-Boot] [PATCH v3 2/3] ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layout Derald D. Woods
2018-03-14 14:09 ` Tom Rini [this message]
2018-02-26 23:52 ` [U-Boot] [PATCH v3 3/3] ARM: omap3: evm: Sync with omap3_beagle configuration Derald D. Woods
2018-03-14 14:10 ` [U-Boot] [U-Boot, v3, " Tom Rini
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=20180314140959.GY1770@bill-the-cat.ec.rr.com \
--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