some additional work to get it to work on these, but that's
to be done in a separate set.
Any comment is of course appreciated,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
signature.asc
Description: Digital
Hi,
On Mon, Oct 06, 2014 at 01:47:28PM +0200, Maxime Ripard wrote:
> Hi,
>
> Since this patchset is rather big, I didn't posted it by mail, but as
> suggested on the openwrt documentation, hosted these patches on a
> server.
>
> This serie of patches aims at using th
OverlayFS version 23 and later require an additional directory to be given at
mount time.
Add a patch to the fstools to first test wether it can mount it without (for
older versions), and if not, use the new mechanism.
Signed-off-by: Maxime Ripard
---
...s-mount-Support-latest-overlayfs
ECC_strength.patch
* 011-pxa3xx_nand_clean_error_handling.patch
* 012-pxa3xx_nand_use_ecc_info_from_dt.patch
* 018-decouple_phy_id_and_address.patch
* 019-add_fixed_phy_register.patch
* 020-of_fixed_link_phy.patch
* 021-mvneta_support_fixed_links.patch
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Androi
igned-off-by: Maxime Ripard
---
scripts/ubinize-image.sh | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/ubinize-image.sh b/scripts/ubinize-image.sh
index 6762c22bc4a6..11c25ecc8ee1 100755
--- a/scripts/ubinize-image.sh
+++ b/scripts/ubinize-image.sh
@@ -25,13 +
The mvebu image Makefile directly calls the padjffs2 utility, while there's an
generic make function to do just that. Switch to it
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/
Hi,
This patch adds a new profile for the Mirabox, and fixes a few things
along the way, mostly because of the Mirabox NAND page size that
differs from the other mvebu boards (and most of the boards supported
by OpenWRT apparently).
Thanks,
Maxime
Maxime Ripard (4):
mvebu: Replace the
The GlobalScale Mirabox features an Armada 370, with 1GB of NAND and 1GB of
RAM, 2 Gigabit Ethernet ports, 2 USB3 ports, and a wifi bgn chip.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/profiles/110-mirabox.mk | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
The page size and related NAND options are completely board specific. It makes
little sense to define such options in the global image Makefile.
Move these informations to the profiles, where it is more fit.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 5
Hi Imre,
On Thu, Oct 09, 2014 at 10:30:46PM +0200, Imre Kaloz wrote:
> Hi,
>
> On Thu, 09 Oct 2014 17:59:25 +0200, Maxime Ripard
> wrote:
>
> >This patch adds a new profile for the Mirabox, and fixes a few things
> >along the way, mostly because of the Mirabox NAN
Hi Daniel,
On Sun, Oct 26, 2014 at 11:37:18PM +0100, Daniel Golle wrote:
> Hi Maxime,
>
> On Thu, Oct 09, 2014 at 05:59:27PM +0200, Maxime Ripard wrote:
> > On boards with large page size, the rootfs we generate might end up using
> > less
> > PEB than the minimum n
Hi,
On Thu, Oct 09, 2014 at 04:48:48PM +0200, Maxime Ripard wrote:
> OverlayFS version 23 and later require an additional directory to be given at
> mount time.
>
> Add a patch to the fstools to first test wether it can mount it without (for
> older versions), and if not, use th
Hi,
On Thu, Oct 09, 2014 at 05:10:25PM +0200, Maxime Ripard wrote:
> Hi,
>
> This is the second version of my rather big changes to support the
> 3.16 kernel, and more specifically on the mvebu SoCs.
>
> The first patch ports the existing 3.14 patches to 3.16, and c
Hi Rafał,
On Tue, Oct 28, 2014 at 04:29:15PM +0100, Rafał Miłecki wrote:
> Hi Maxime,
>
> On 9 October 2014 17:10, Maxime Ripard
> wrote:
> > This is the second version of my rather big changes to support the
> > 3.16 kernel, and more specifically on the mvebu SoCs.
Hi,
On Tue, Oct 28, 2014 at 06:38:00PM +0100, Rafał Miłecki wrote:
> On 28 October 2014 16:59, Maxime Ripard
> wrote:
> > On Tue, Oct 28, 2014 at 04:29:15PM +0100, Rafał Miłecki wrote:
> >> On 9 October 2014 17:10, Maxime Ripard
> >> wrote:
> >> > T
Hi Imre,
On Thu, Oct 09, 2014 at 10:54:19PM +0200, Maxime Ripard wrote:
> Hi Imre,
>
> On Thu, Oct 09, 2014 at 10:30:46PM +0200, Imre Kaloz wrote:
> > Hi,
> >
> > On Thu, 09 Oct 2014 17:59:25 +0200, Maxime Ripard
> > wrote:
> >
> > >This patch
mvebu patches were sent fine. I was thinking about
> v2-0002-mvebu-Add-3.16-kernel-patches-and-configuration.patch
> v2-0003-mvebu-Switch-to-3.16.patch
> When working on mvebu target and 3.18 support please kindly send them
> as e-mail patches.
Yeah, I sent them that way bec
On Mon, Oct 27, 2014 at 11:16:13AM +0100, Maxime Ripard wrote:
> Hi Daniel,
>
> On Sun, Oct 26, 2014 at 11:37:18PM +0100, Daniel Golle wrote:
> > Hi Maxime,
> >
> > On Thu, Oct 09, 2014 at 05:59:27PM +0200, Maxime Ripard wrote:
> > > On boards with large pag
On Wed, Oct 29, 2014 at 11:42:13AM +0100, Maxime Ripard wrote:
> Hi Imre,
>
> On Thu, Oct 09, 2014 at 10:54:19PM +0200, Maxime Ripard wrote:
> > Hi Imre,
> >
> > On Thu, Oct 09, 2014 at 10:30:46PM +0200, Imre Kaloz wrote:
> > > Hi,
> > >
> >
ce it
directly references a variable that will not be declared if
CONFIG_BRIDGE_NETFILTER is not set. Protect the variable affectations by an
ifdef to make sure this doesn't happen.
Signed-off-by: Maxime Ripard
---
.../644-bridge_optimize_netfilter_hooks.patch | 43 +++-
developpers mental health.
Signed-off-by: Maxime Ripard
---
include/kernel-defaults.mk | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/include/kernel-defaults.mk b/include/kernel-defaults.mk
index 8abd32d7141d..e78ced7e818a 100644
--- a/include/kernel
The 3.18 kernel introduced new Kconfig options for the xt_nat and iptable_nat
kernel modules, that both belong to the ipt_nat kernel package.
Enable this new options.
Signed-off-by: Maxime Ripard
---
include/netfilter.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include
Hi Felix,
On Sun, Nov 09, 2014 at 11:54:15AM +0100, Felix Fietkau wrote:
> On 2014-11-07 11:58, Maxime Ripard wrote:
> > Rely on the Kconfig defconfig mechanism to fill all the missing options,
> > instead of needing to set them all in the kernel configurations like what
> &g
On Thu, Nov 06, 2014 at 05:48:19PM +0100, Maxime Ripard wrote:
> On Wed, Oct 29, 2014 at 11:42:13AM +0100, Maxime Ripard wrote:
> > Hi Imre,
> >
> > On Thu, Oct 09, 2014 at 10:54:19PM +0200, Maxime Ripard wrote:
> > > Hi Imre,
> > >
> > > On T
On Thu, Nov 06, 2014 at 05:47:46PM +0100, Maxime Ripard wrote:
> On Mon, Oct 27, 2014 at 11:16:13AM +0100, Maxime Ripard wrote:
> > Hi Daniel,
> >
> > On Sun, Oct 26, 2014 at 11:37:18PM +0100, Daniel Golle wrote:
> > > Hi Maxime,
> > >
> > >
On Sun, Nov 16, 2014 at 10:54:18AM +0100, Daniel Golle wrote:
> Hi Maxime,
>
> first of all sorry for the late reply.
>
> On Mon, Oct 27, 2014 at 11:16:13AM +0100, Maxime Ripard wrote:
> > Hi Daniel,
> > > This will break things if rootfs is a read-write UBIF
Hi Felix,
On Sun, Nov 09, 2014 at 11:54:15AM +0100, Felix Fietkau wrote:
> On 2014-11-07 11:58, Maxime Ripard wrote:
> > Rely on the Kconfig defconfig mechanism to fill all the missing options,
> > instead of needing to set them all in the kernel configurations like what
> &g
On Sun, Nov 23, 2014 at 06:38:18PM -0800, Florian Fainelli wrote:
> Le 07/11/2014 07:20, Maxime Ripard a écrit :
> > The 3.18 kernel introduced new Kconfig options for the xt_nat and
> > iptable_nat
> > kernel modules, that both belong to the ipt_nat kernel package.
>
both the log and
the generated kernel configuration file from:
http://free-electrons.com/~maxime/pub/openwrt/config-backup-with/
http://free-electrons.com/~maxime/pub/openwrt/config-backup-without/
This has been generated with the following script:
http://code.bulix.org/bbs1p3-87473
Maxime
Maxime
Hi Florian,
On Sun, Nov 23, 2014 at 06:42:25PM -0800, Florian Fainelli wrote:
> Le 18/11/2014 02:27, Maxime Ripard a écrit :
> > Hi Felix,
> >
> > On Sun, Nov 09, 2014 at 11:54:15AM +0100, Felix Fietkau wrote:
> >> On 2014-11-07 11:58, Maxime Ripard wrote:
>
developpers mental health.
Signed-off-by: Maxime Ripard
---
include/kernel-defaults.mk | 40
1 file changed, 32 insertions(+), 8 deletions(-)
diff --git a/include/kernel-defaults.mk b/include/kernel-defaults.mk
index 8abd32d7141d..9fd96a234e37 100644
--- a
On Tue, Nov 25, 2014 at 11:21:22AM +0100, Felix Fietkau wrote:
> On 2014-11-24 22:42, Maxime Ripard wrote:
> > Rely on the Kconfig defconfig mechanism to fill all the missing options,
> > instead of needing to set them all in the kernel configurations like what
> > wa
Switch to a dumber implementation that will be easier to maintain in the long
run, with only if statements instead of having nested subst calls.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 25 +
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a
x64 is handled by the x86 architecture in Linux, add a case for it in
LINUX_KARCH.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/kernel.mk b/include/kernel.mk
index 97eb1f74f4f7..2d15e9ad2712 100644
--- a/include/kernel.mk
+++ b
developers mental health.
Signed-off-by: Maxime Ripard
---
include/kernel-defaults.mk | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/include/kernel-defaults.mk b/include/kernel-defaults.mk
index 8abd32d7141d..493e96372eef 100644
--- a/include/kernel
from v2:
- Rebased on current master
- Refactored LINUX_KARCH affectation, added a test case for x64 and
used it.
Changes from v1:
- Added a test case for OpenWRT architectures name that don't match
Linux'
Maxime Ripard (4):
kernel.mk: Refactor LINUX_KARCH affectation
Hi Jonas,
On Fri, Nov 28, 2014 at 10:19:28PM +0100, Jonas Gorski wrote:
> On Fri, Nov 28, 2014 at 7:20 PM, Maxime Ripard
> wrote:
> > Switch to a dumber implementation that will be easier to maintain in the
> > long
> > run, with only if statements instead of h
The mvebu image Makefile directly calls the padjffs2 utility, while there's an
generic make function to do just that. Switch to it
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/
igned-off-by: Maxime Ripard
---
scripts/ubinize-image.sh | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/ubinize-image.sh b/scripts/ubinize-image.sh
index 6762c22bc4a6..11c25ecc8ee1 100755
--- a/scripts/ubinize-image.sh
+++ b/scripts/ubinize-image.sh
@@ -25,13 +
Create a generic board relying on the board mechanism we just introduced.
So far, the behaviour hasn't really changed, the same boards are supported,
with the same options.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/boards/generic.mk | 18 ++
target/linux/mvebu/
the
$(PLATFORM_DIR)/boards directory, to set up this kind of board specific
options, that we always want to be in-use, no matter what profile is used.
Signed-off-by: Maxime Ripard
---
include/target.mk | 12
1 file changed, 12 insertions(+)
diff --git a/include/target.mk b/include
found good enough, this will
obviously need some fixing.
- Some part of the DTB/Boards loop probably should go into the core code,
since it will probably be reused by a lot of other platforms too.
Let me know what you think,
Maxime
Maxime Ripard (5):
mvebu: Replace the padjffs2 call b
The Mirabox has different NAND options than the one used in the generic board,
mostly because of its 512k page size.
Add a new board for it.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/boards/generic.mk | 1 -
target/linux/mvebu/boards/mirabox.mk | 13 +
2 files changed
Switch to a dumber implementation that will be easier to maintain in the long
run, with only if statements instead of having nested subst calls.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/include
x64 is handled by the x86 architecture in Linux, add a case for it in
LINUX_KARCH.
Signed-off-by: Maxime Ripard
---
include/kernel.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/kernel.mk b/include/kernel.mk
index b905cb9e1936..eeb0c3d2bd8e 100644
--- a/include
of if .. else if statements
Changes from v2:
- Switch to LINUX_KARCH for the kernel arch instead of relying on
our own logic
Changes from v1:
- Add some logic to compute the linux kernel architecture that
doesn't always equal to ARCH
Maxime Ripard (4):
kernel.mk: Ref
developers mental health.
Signed-off-by: Maxime Ripard
---
include/kernel-defaults.mk | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/include/kernel-defaults.mk b/include/kernel-defaults.mk
index d6c892462359..cc03e31efab4 100644
--- a/include/kernel
On Fri, Dec 12, 2014 at 06:45:06PM +0100, Jonas Gorski wrote:
> On Fri, Dec 12, 2014 at 5:02 PM, Maxime Ripard
> wrote:
> > Now that we use the defconfigs, we can remove all the options at their
> > default
> > value.
>
> This causes a lot of kernel-config ch
ask about about
> everything that is at its defaultvalue, while finishing any *config
> will result all default values to be added to the config-* in
> target/linux//. This might be easily fixable by running make
> savedefconfig first before the openwrt scripts create the difference
&g
tion kind of defeats the
original purpose of this patch set.
So I guess we should define a policy on this. What do you think?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
signature.asc
Description: Digital signature
Hi Felix,
On Tue, Dec 16, 2014 at 10:15:41AM +0100, Felix Fietkau wrote:
> On 2014-12-12 16:21, Maxime Ripard wrote:
> > Even though we always build all the board images for a given target, some
> > options widely differ from one board to another when it comes to hardware
&g
On Tue, Dec 16, 2014 at 01:43:03PM +0100, Jonas Gorski wrote:
> On Mon, Dec 15, 2014 at 2:17 PM, Maxime Ripard
> wrote:
> > On Sat, Dec 13, 2014 at 07:50:52PM +0100, Jonas Gorski wrote:
> >> > Ok, I think most of it is because of options enabled by default. I
> >>
The mvebu image Makefile directly calls the padjffs2 utility, while there's an
generic make function to do just that. Switch to it
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/
The mvebu image makefile define something almost identical to the generic
implementation found in include/image.mk.
Switch to this implementation.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a
Some devices out there only have a NOR flash to store the rootfs on.
While using UBI is arguable on this kind of NAND, this is something that should
be supported.
Signed-off-by: Maxime Ripard
---
.../490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch | 5 +++--
.../490-ubi-auto
a more specific behaviour, like Mamba expects for example.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 96 ++-
1 file changed, 74 insertions(+), 22 deletions(-)
diff --git a/target/linux/mvebu/image/Makefile
b/target/linux/mvebu
for the others.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/target/linux/mvebu/image/Makefile
b/target/linux/mvebu/image/Makefile
index 40a06c3e1443..a10e1f052fbe 100644
--- a/target
The 3.16 kernel introduced support for the A38x SoC family. In order to support
them, switch to the newer 3.18 kernel.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/Makefile b/target/linux
While we supported only the NAND so far, some boards use a NOR, which requires
a different set of UBI options.
Add a new subprofile type for such boards.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 26 ++
1 file changed, 26 insertions(+)
diff
The Armada 385 DB AP board is a reference design board for access
points.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 1 +
...nctrl-mvebu-a38x-Add-UART1-muxing-options.patch | 43
.../013-ARM-mvebu-a38x-Fix-node-names.patch| 98
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
Maxime Ripard (9):
mvebu: Replace the padjffs2 call by the generic definition
mvebu: Switch to the generic mkuimage macro
kernel
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 1 +
.../020-armada-385-rd-mtd-partitions.patch | 24 ++
2 files changed, 25 insertions(+)
create mode 100644
target/linux/mvebu/patches-3.18/020-armada-385-rd-mtd
On Wed, Jan 14, 2015 at 12:43:25PM +0100, Rafał Miłecki wrote:
> On 13 January 2015 at 16:56, Maxime Ripard
> wrote:
> > Some devices out there only have a NOR flash to store the rootfs on.
> >
> > While using UBI is arguable on this kind of NAND, this is something
Hi Imre,
On Wed, Jan 14, 2015 at 12:50:55PM +0100, Imre Kaloz wrote:
> On Tue, 13 Jan 2015 16:56:45 +0100, Maxime Ripard
> wrote:
>
> >++ partition@2 {
> >++
Hi,
On Wed, Jan 14, 2015 at 01:03:49PM +0100, Imre Kaloz wrote:
> Hi Maxime,
>
> On Tue, 13 Jan 2015 16:56:41 +0100, Maxime Ripard
> wrote:
>
> >+$(eval $(call MultiProfile,Generic,$(PROFILES_LIST)))
> >+$(eval $(call MultiProfile,Evalboards,$(PROFILES_LIST)))
&
On Wed, Jan 14, 2015 at 12:52:56PM +0100, Imre Kaloz wrote:
> On Tue, 13 Jan 2015 16:56:46 +0100, Maxime Ripard
> wrote:
>
> >+diff --git a/arch/arm/boot/dts/armada-385-db-ap.dts
> >b/arch/arm/boot/dts/armada-385-db-ap.dts
> >+index 02db04867d8f..2a58443e2504 100644
On Fri, Jan 16, 2015 at 04:38:47PM +0100, Imre Kaloz wrote:
> On Fri, 16 Jan 2015 16:23:43 +0100, Maxime Ripard
> wrote:
>
> >Hi Imre,
> >
> >On Wed, Jan 14, 2015 at 12:50:55PM +0100, Imre Kaloz wrote:
> >>On Tue, 13 Jan 2015 16:5
Hi,
On Wed, Jan 14, 2015 at 01:37:37PM +0100, Maxime Ripard wrote:
> On Wed, Jan 14, 2015 at 12:43:25PM +0100, Rafał Miłecki wrote:
> > On 13 January 2015 at 16:56, Maxime Ripard
> > wrote:
> > > Some devices out there only have a NOR flash to store the rootfs on.
> &
Hi,
On Fri, Jan 23, 2015 at 01:57:44PM +0100, Imre Kaloz wrote:
> On Thu, 22 Jan 2015 11:33:14 +0100, Maxime Ripard
> wrote:
>
> >Hi,
> >
> >On Wed, Jan 14, 2015 at 01:37:37PM +0100, Maxime Ripard wrote:
> >>On Wed, Jan 14, 2015 at 12:43:25PM +0100, Rafał Mił
On Sun, Jan 25, 2015 at 08:50:32PM +0100, Imre Kaloz wrote:
> Hi,
>
> On Sun, 25 Jan 2015 18:06:03 +0100, Maxime Ripard
> wrote:
>
> >>Sure, but please implement UBI on NOR as a generic solution.
> >
> >What do you mean? It already works quite well (with t
We're going to need the MTD split related options for our NOR support.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/config-3.18 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target/linux/mvebu/config-3.18 b/target/linux/mvebu/config-3.18
index 096b5ed0180b..b4a372d7db72 1
Some devices out there only have a NOR flash to store the rootfs on.
While using UBI is arguable on this kind of NAND, this is something that should
be supported.
Signed-off-by: Maxime Ripard
---
.../490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch | 5 +++--
.../490-ubi-auto
a more specific behaviour, like Mamba expects for example.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 96 ++-
1 file changed, 74 insertions(+), 22 deletions(-)
diff --git a/target/linux/mvebu/image/Makefile
b/target/linux/mvebu
While we supported only the NAND so far, some boards use a large enough NOR,
where UBI is the only reasonable option. Create a new sub-profile template with
a different set of UBI options.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 22 ++
1 file
Some boards only come with a small NOR on it, where UBI isn't a good solution
because of its overhead.
Add a new subprofile for such boards, that rely on the mtd split framework
instead.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 25 +
1
chip datasheet for the others.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/target/linux/mvebu/image/Makefile
b/target/linux/mvebu/image/Makefile
index a8fc4de134f8..c8ec72e87ce3 100644
--- a
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 3 +++
.../207-armada-385-rd-mtd-partitions.patch| 19 +++
2 files changed, 22 insertions(+)
create mode 100644
target/linux/mvebu/patches-3.18/207-armada-385-rd-mtd
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 an
The Armada 385 DB AP board is a reference design board for access
points.
Signed-off-by: Maxime Ripard
---
target/linux/mvebu/image/Makefile | 1 +
...019-mtd-nand-pxa3xx-Fix-PIO-FIFO-draining.patch | 97 +
...M-mvebu-Add-a-number-of-pinctrl-functions.patch | 70
Hi,
On Thu, Feb 05, 2015 at 12:39:18PM +0100, Imre Kaloz wrote:
> Hi Maxime,
>
> On Wed, 04 Feb 2015 15:36:58 +0100, Maxime Ripard
> wrote:
>
>
>
> >It builds up on that to then introduce support for two Armada
> >385-based evaluations boards from Marvell.
In order for the image to be built, some patches need to be ported to 3.19.
Add the relevant patches. Note that most of them (if not all) should be merged
in 3.20, removing the need to carry them on then.
Signed-off-by: Maxime Ripard
---
...019-mtd-nand-pxa3xx-Fix-PIO-FIFO-draining.patch | 97
81 matches
Mail list logo
