* why is entire 8xx architecture defined as "broken"?
@ 2005-03-25 22:41 Robert P. J. Day
0 siblings, 0 replies; only message in thread
From: Robert P. J. Day @ 2005-03-25 22:41 UTC (permalink / raw)
To: Embedded PPC Linux list
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-03-25 22:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-25 22:41 why is entire 8xx architecture defined as "broken"? Robert P. J. Day
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).