From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: why is entire 8xx architecture defined as "broken"?
Date: Fri, 25 Mar 2005 17:41:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.61.0503251733170.18399@localhost.localdomain> (raw)
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
reply other threads:[~2005-03-25 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0503251733170.18399@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).