From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/4] lpc32xx: devkit3250 board update
Date: Mon, 10 Aug 2015 17:34:14 +0300 [thread overview]
Message-ID: <55C8B666.9070909@mleia.com> (raw)
In-Reply-To: <1437173180-28466-1-git-send-email-vz@mleia.com>
Hello Albert,
On 18.07.2015 01:46, Vladimir Zapolskiy wrote:
> This changeset improves support of Timll DevKit3250 board:
> * added LPC32xx MAC and SMSC RMII phy support, this dependends on
> - http://patchwork.ozlabs.org/patch/489100/
> - http://patchwork.ozlabs.org/patch/489190/
> - http://patchwork.ozlabs.org/patch/491419/
> - http://patchwork.ozlabs.org/patch/491420/
> * added GPIO, SPI, I2C support, works good, many thanks to Albert,
> * added LPC32xx SLC NAND driver, testing of 50 MiB data raw reading
> shows 1 MiB/s speed, the same change has been sent to the mailing
> list separately, here it is duplicated as a build dependency:
> - http://patchwork.ozlabs.org/patch/495247/
> - http://patchwork.ozlabs.org/patch/495250/
> * added an option to pass DTB to an operating system,
> * changed serial console to commonly used as default UART5,
> * boot delay is set to 1 for convenience,
> * extended predefined environment variables and reserved space on NAND,
> * added an option to build SPL image for the board, by default SPL
> downloads U-boot image from NAND (offset 0x40000, size 0x60000).
>
> Changes from v1 to v2:
> * addressed Albert's and Scott's comments to LPC32xx SLC NAND driver,
> see patch v2 2/4,
> * added Tegra and TI maintainers to Cc list to review/ack a change 1/4
> in simple NAND SPL framework, which potentially (very unlikely)
> may cause a regression in NAND SPL on Tegra, TI OMAP or TI DaVinci
> platforms.
>
> Previous version of the change and discussion can be found here:
> http://lists.denx.de/pipermail/u-boot/2015-July/219253.html
>
> Albert, from commit logs I noticed that WORK92105 has SLC NAND chip,
> but it is managed by MLC controller, if you have any plans to test
> LPC32xx SLC NAND driver from the series, please *be aware* of
> different OOB layouts, I found it is quite easy to screw up the chip,
> if SLC and MLC are interchanged, so that only "nand scrub" helps.
> FWIW this SLC NAND driver uses a default OOB layout, the same one
> is found in Linux LPC32xx SLC NAND driver.
>
> Vladimir Zapolskiy (4):
> spl: nand: simple: replace readb() with chip specific read_buf()
> nand: lpc32xx: add SLC NAND controller support
> lpc32xx: devkit3250: update of board configuration
> lpc32xx: devkit3250: add spl build support
do you see any left issues in this series or in MAC series mentioned on
top? If no, please could you apply these 8 patches?
Thank you in advance.
--
With best wishes,
Vladimir
prev parent reply other threads:[~2015-08-10 14:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 22:46 [U-Boot] [PATCH v2 0/4] lpc32xx: devkit3250 board update Vladimir Zapolskiy
2015-07-17 22:47 ` [U-Boot] [PATCH v2 1/4] spl: nand: simple: replace readb() with chip specific read_buf() Vladimir Zapolskiy
2015-07-28 1:22 ` Scott Wood
2015-08-13 13:18 ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-07-17 22:47 ` [U-Boot] [PATCH v2 2/4] nand: lpc32xx: add SLC NAND controller support Vladimir Zapolskiy
2015-07-17 23:12 ` Scott Wood
2015-07-17 23:38 ` Vladimir Zapolskiy
2015-07-17 23:53 ` Scott Wood
2015-07-17 23:55 ` Scott Wood
2015-07-18 0:05 ` Vladimir Zapolskiy
2015-07-17 23:49 ` [U-Boot] [PATCH v3 " Vladimir Zapolskiy
2015-07-18 0:07 ` [U-Boot] [PATCH v4 " Vladimir Zapolskiy
2015-07-27 16:25 ` Vladimir Zapolskiy
2015-07-28 1:23 ` Scott Wood
2015-07-29 18:46 ` LEMIEUX, SYLVAIN
2015-08-13 13:18 ` [U-Boot] [U-Boot, v4, " Tom Rini
2015-07-17 22:47 ` [U-Boot] [PATCH v2 3/4] lpc32xx: devkit3250: update of board configuration Vladimir Zapolskiy
2015-08-13 13:18 ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-07-17 22:47 ` [U-Boot] [PATCH v2 4/4] lpc32xx: devkit3250: add spl build support Vladimir Zapolskiy
2015-08-13 13:18 ` [U-Boot] [U-Boot, v2, " Tom Rini
2015-08-10 14:34 ` Vladimir Zapolskiy [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=55C8B666.9070909@mleia.com \
--to=vz@mleia.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