[OpenWrt-Devel] [PATCH v2 0/8] mvebu: Fix flash support and support for A38x

[Maxime Ripard]

Hi,

This serie aims at finally fixing the already supported mvebu boards
images, since none of them actually work on the boards except for the
WRT1900AC.

This is the follow-up of two previous attempts at doing that:
https://lists.openwrt.org/pipermail/openwrt-devel/2014-October/028593.html
https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029899.html
https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030502.html

In this version, yet another approach has been taken, similar to the
one used for the ar71xx, where each profiles are split in a various
number of subprofiles (1-X), each subprofile representing a
combination of a DT name and its associated UBI options.

It builds up on that to then introduce support for two Armada
385-based evaluations boards from Marvell.

Let me know what you think,
Maxime

Changes from v1:
  - Rebased on top of master
  - Created a new sub-profile for small NOR where UBI cannot be used
    (or doesn't make sense).
  - Removed the sysupgrade generation for the NOR-based boards
  - changed the MTD partition names for the A385 RD and AP boards
  - Added a patch on the NAND driver that fixes timeout issues seen on
    the Armada 385 AP board.

Maxime Ripard (8):
  mvebu: 3.18: Add MTD split framework support
  kernel: Allow ubi autoattach to run on NOR flash
  mvebu: Add sub-profiles
  mvebu: Add large NOR sub-profile implementation
  mvebu: Add a subprofile for boards based on a small NOR
  mvebu: Fix NAND and NOR options
  mvebu: Add the Armada 385 Reference Design support
  mvebu: Add Armada 385 DB AP support

 ...tach-mtd-device-named-ubi-or-data-on-boot.patch |   5 +-
 ...tach-mtd-device-named-ubi-or-data-on-boot.patch |   5 +-
 ...tach-mtd-device-named-ubi-or-data-on-boot.patch |   5 +-
 target/linux/mvebu/config-3.18                     |   2 +
 target/linux/mvebu/image/Makefile                  | 151 +++++++++++---
 ...019-mtd-nand-pxa3xx-Fix-PIO-FIFO-draining.patch |  97 +++++++++
 ...M-mvebu-Add-a-number-of-pinctrl-functions.patch |  70 +++++++
 ...dd-Armada-385-Access-Point-Development-Bo.patch | 220 +++++++++++++++++++++
 ...-mvebu-A385-AP-Enable-the-NAND-controller.patch |  39 ++++
 ...nctrl-mvebu-a38x-Add-UART1-muxing-options.patch |  43 ++++
 .../024-ARM-mvebu-a38x-Fix-node-names.patch        |  98 +++++++++
 .../207-armada-385-rd-mtd-partitions.patch         |  19 ++
 .../208-ARM-mvebu-385-ap-Add-partitions.patch      |  39 ++++
 13 files changed, 765 insertions(+), 28 deletions(-)
 create mode 100644 target/linux/mvebu/patches-3.18/019-mtd-nand-pxa3xx-Fix-PIO-FIFO-draining.patch
 create mode 100644 target/linux/mvebu/patches-3.18/020-ARM-mvebu-Add-a-number-of-pinctrl-functions.patch
 create mode 100644 target/linux/mvebu/patches-3.18/021-ARM-mvebu-Add-Armada-385-Access-Point-Development-Bo.patch
 create mode 100644 target/linux/mvebu/patches-3.18/022-ARM-mvebu-A385-AP-Enable-the-NAND-controller.patch
 create mode 100644 target/linux/mvebu/patches-3.18/023-pinctrl-mvebu-a38x-Add-UART1-muxing-options.patch
 create mode 100644 target/linux/mvebu/patches-3.18/024-ARM-mvebu-a38x-Fix-node-names.patch
 create mode 100644 target/linux/mvebu/patches-3.18/207-armada-385-rd-mtd-partitions.patch
 create mode 100644 target/linux/mvebu/patches-3.18/208-ARM-mvebu-385-ap-Add-partitions.patch

-- 
2.2.2
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel