On 1 August 2013 07:57, Andy Green <andy.gr...@linaro.org> wrote:
> On 1 August 2013 14:11, Viresh Kumar <viresh.ku...@linaro.org> wrote:
>> Hi Andrey,
>>
>> linaro/configs/* is getting bigger and bigger, probably its the right time to
>> organize it better for the future. There can be multiple things that we can
>> do to avoid confusions of names but for now probably we can create
>> separate directories for boards, rootfs & kernel fragments? Or some
>> other idea that you might have?
>
> Just a thought these seem to me like they are covering up for missing
> "select xxx" in the related Kconfig option (eg, CONFIG_ANDROID), or
> stuff that should be in the defconfig (eg, omap4, vexpress).

Is the platform specific defconfig still relevant in a multiarch
kernel?  I guess the fragments should adding items missing from the
default multiarch config.  Excuse my ignorance, 'cause I don't know
how multiarch works...

Historically, the main reason for us creating the frags was because of
the platforms (eg, Ubuntu) adding lots of config options that weren't
in the defconfig.  The vexpress defconfig has always been broken.  But
over-riding the defconfig with Ubuntu/Android/whatever options was a
bigger bodge than creating fragments.

So I think they are still important for Linaro's builds.  Escpecially
as we aren't building multiarch kernels for all our platforms yet.


>
> There's also an issue the fragments are all =y when for
> ARCH_MULTIPLATFORM, it implies all things not needed for rootfs mount
> need to be =m.

That's a good point and something we should look into.  We should
really be using multiarch kernels sooner rather than later, right?

>
> -Andy
>
>> --
>> viresh
>>
>> _______________________________________________
>> linaro-dev mailing list
>> linaro-dev@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-dev
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to