why is entire 8xx architecture defined as "broken"?
Robert P. J. Day
rpjday at mindspring.com
Sat Mar 26 09:41:25 EST 2005
after i looked at the Kconfig setup for 2.6.11-5, i'm a bit puzzled
-- why is the entire 8xx architecture defined as "BROKEN"? follow the
logic along:
arch/ppc/Kconfig:
config 8xx
depends on BROKEN
bool "8xx"
and what means "BROKEN"?
init/Kconfig:
config BROKEN
bool
depends on !CLEAN_COMPILE
default y
ok, and "CLEAN_COMPILE"? defined just above that:
config CLEAN_COMPILE
bool "Select only drivers expected to compile cleanly" if
EXPERIMENTAL
default y
ok, and "EXPERIMENTAL"?
config EXPERIMENTAL
bool "Prompt for development and/or incomplete code/drivers"
and *that* refers to the top-level menu entry regarding whether you
want to take a chance on "development and/or incomplete code/drivers",
not entire architectures.
the above seems just a tad misleading, no?
rday
More information about the Linuxppc-embedded
mailing list