* ppc85xx_basic_defconfig is buggy ?
@ 2019-05-23 7:52 Christophe Leroy
2019-05-28 8:13 ` Michael Ellerman
0 siblings, 1 reply; 2+ messages in thread
From: Christophe Leroy @ 2019-05-23 7:52 UTC (permalink / raw)
To: linuxppc-dev, Paul Mackerras
ppc85xx_basic_defconfig doesn't not select CONFIG_PPC_85xx.
Is that expected ?
Christophe
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ppc85xx_basic_defconfig is buggy ?
2019-05-23 7:52 ppc85xx_basic_defconfig is buggy ? Christophe Leroy
@ 2019-05-28 8:13 ` Michael Ellerman
0 siblings, 0 replies; 2+ messages in thread
From: Michael Ellerman @ 2019-05-28 8:13 UTC (permalink / raw)
To: Christophe Leroy, linuxppc-dev, Paul Mackerras
Christophe Leroy <christophe.leroy@c-s.fr> writes:
> ppc85xx_basic_defconfig doesn't not select CONFIG_PPC_85xx.
You mean arch/powerpc/configs/mpc85xx_basic_defconfig presumably.
> Is that expected ?
Yeah it is expected.
It's not intended to be a full defconfig, it's used as a fragment and
merged with other configs, see arch/powerpc/Makefile:
PHONY += mpc85xx_defconfig
mpc85xx_defconfig:
$(call merge_into_defconfig,mpc85xx_basic_defconfig,\
85xx-32bit 85xx-hw fsl-emb-nonhw)
Where 85xx-32bit.config is:
CONFIG_HIGHMEM=y
CONFIG_KEXEC=y
CONFIG_PPC_85xx=y
CONFIG_PROC_KCORE=y
CONFIG_PHYS_64BIT=y
So that's where PPC_85xx gets set.
But it's confusing that mpc85xx_basic_defconfig is named "foo_defconfig"
but is not actually a proper defconfig. We should rename it to
mpc85xx_basic.config to make it clearer that it's a fragment. I'll do a
patch.
cheers
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-28 8:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-23 7:52 ppc85xx_basic_defconfig is buggy ? Christophe Leroy
2019-05-28 8:13 ` Michael Ellerman
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.