[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#670462: linux-2.6: Support new armhf kernel variant for Versatile Express (vexpress)



Vagrant Cascadian <vagrant@freegeek.org> writes:

Hi.

> The following trimmed down debian/config/armhf/config.vexpress still worked 
> for me in qemu (built against 3.2.16-1). It also trimmed out the extraneous 
> "Supported" text in the defines file. The control file can be generated, as I 
> understand it, so didn't include in this diff.
>
> diff -u linux-2.6-3.2.16/debian/config/armhf/defines linux-2.6-3.2.16/debian/config/armhf/defines
> --- linux-2.6-3.2.16/debian/config/armhf/defines
> +++ linux-2.6-3.2.16/debian/config/armhf/defines
> @@ -2,6 +2,7 @@
>  flavours:
>   mx5
>   omap
> + vexpress
>  kernel-arch: arm
>  
>  [image]
> @@ -28,0 +30,8 @@
> +
> +[vexpress_build]
> +image-file: arch/arm/boot/zImage
> +
> +[vexpress_description]
> +hardware: ARM Ltd. Versatile Express
> +hardware-long: ARM Ltd. Versatile Express family of processors
> +
>
> only in patch2:
> unchanged:
> --- linux-2.6-3.2.16.orig/debian/config/armhf/config.vexpress
> +++ linux-2.6-3.2.16/debian/config/armhf/config.vexpress
> @@ -0,0 +1,54 @@
> +##
> +## file: arch/arm/Kconfig
> +##
> +## choice: ARM system type
> +CONFIG_ARCH_VEXPRESS=y
> +## end choice
> +
> +## arch/arm/mach-vexpress/Kconfig
> +CONFIG_ARCH_VEXPRESS_CA9X4=y
> +
> +CONFIG_LOG_BUF_SHIFT=14

any reason for this change ?

> +CONFIG_OPROFILE=m
> +
> +CONFIG_SMP=y
> +CONFIG_VMSPLIT_2G=y
> +CONFIG_HOTPLUG_CPU=y
> +
> +CONFIG_ZBOOT_ROM_TEXT=0x0
> +CONFIG_ZBOOT_ROM_BSS=0x0
> +
> +CONFIG_NEON=y
> +
> +
> +CONFIG_MTD=m

hm. why is it still enabled ? from what I understand, qemu vexpress doesn't
simulate the flash peripheral. If you want to support something else
than qemu, you're missing some drivers I guess. If you want to support
only qemu vexpress emulation, maybe it worthes to be mentionned in the
description ?

> +CONFIG_MTD_CONCAT=m
> +CONFIG_MTD_PARTITIONS=m
> +CONFIG_MTD_CMDLINE_PARTS=m
> +CONFIG_MTD_CHAR=m
> +CONFIG_MTD_BLOCK=m
> +CONFIG_MTD_CFI=m
> +CONFIG_MTD_CFI_INTELEXT=m
> +CONFIG_MTD_CFI_AMDSTD=m
> +CONFIG_MTD_ARM_INTEGRATOR=m

fwiw, doesn't exist anymore. physmap should be used now.

Nevertheless, I've built tested this configuration and it worked in Qemu
as expected. I'll add that once we agree on the configuration. Also, do
you intend to add support for it into the debian-installer too ?


Thanks,
Arnaud



Reply to: