On Sun, 2013-03-17 at 08:35 +0900, Nobuhiro Iwamatsu wrote:
> Package: linux
> Version: 3.8.2-1~experimental.1
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> >From linux 3.8, support of armada 370/xp was added in arm.
> This is classified into the armhf architecture of debian.
> First I began and thought that an armada flavor would be added.
> When I consulted about this in debian-arm ML, I got advice from
> several developers what "multiplatform" flavour was better than
> "armada" flavour[0].
>
> Since arm is developed toward multiplatform from now on,
> I think that "multiplatform" is desirable.
> Although there is still little SoC which is supporting
> multiplatform, I would like to support armada 370/xp
> (mach-mvebu) first.
>
> I created the patch which supports this.
> Please check and apply.
In future all ARM kernels should be multi-platform, but I expect there
will still be different flavours, such as for LPAE or the RT featureset.
I would much prefer a name that will provide a more useful distinction
in future (and not be too long!). Perhaps it should refer to the CPU
requirement like the flavours for some other architectures.
> NOTE: The vexpress can also be supported by multiplatform.
> If it is desirable to include this in multiplatform, I will
> create a new patch.
I think that's desirable, but maybe make that a second patch?
The linux-latest package will also need a transitional package to
migrate vexpress installations.
> From: Nobuhiro Iwamatsu
> Date: Mon, 4 Mar 2013 13:20:13 +0900
> Subject: [PATCH] [armhf] Add multiplatform flavour
>
> Signed-off-by: Nobuhiro Iwamatsu
> ---
> debian/config/armhf/config.multiplatform | 96
> ++
> debian/config/armhf/defines | 11
> debian/installer/armhf/kernel-versions |7 ++-
> 3 files changed, 111 insertions(+), 3 deletions(-)
> create mode 100644 debian/config/armhf/config.multiplatform
>
> diff --git a/debian/config/armhf/config.multiplatform
> b/debian/config/armhf/config.multiplatform
> new file mode 100644
> index 000..cb4ad57
> --- /dev/null
> +++ b/debian/config/armhf/config.multiplatform
[...]
> +##
> +## file: drivers/net/ethernet/marvell/Kconfig
> +##
> +CONFIG_NET_VENDOR_MARVELL=y
> +CONFIG_MVMDIO=y
> +CONFIG_MVNETA=y
> +
> +##
> +## file: drivers/net/ethernet/micrel/Kconfig
> +##
> +CONFIG_NET_VENDOR_MICREL=y
> +
> +##
> +## file: drivers/net/phy/Kconfig
> +##
> +CONFIG_PHYLIB=y
> +CONFIG_MARVELL_PHY=y
[...]
Do these all need to be built in? For a multi-platform kernel we should
really be building drivers as modules by default.
Ben.
--
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
- Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'
signature.asc
Description: This is a digitally signed message part
