From: Norbert Kiesel <nkiesel@tbdnetworks.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Alejandro Riveira Fernández" <ariveira@gmail.com>,
"Adrian Bunk" <bunk@stusta.de>,
"Arjan van de Ven" <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
Date: Thu, 14 Dec 2006 16:24:44 +0100 [thread overview]
Message-ID: <1166109884.8815.157.camel@titan.tbdnetworks.com> (raw)
In-Reply-To: <20061214144750.GA4022@ucw.cz>
On Thu, 2006-12-14 at 14:47 +0000, Pavel Machek wrote:
> Hi!
>
> > So far all first-hand experiences I heard of were positive (i.e. I did
> > not get an emaail from anyone saying: It had a negative effect for me),
> > so I propose to apply the patch from Con Kolivas. The wording in the
> > description still very strongly recommends to not change that value, and
> > it's still dependent on EXPERIMENTAL. I append the patch just because
>
> There's a big difference between 'experimental' and 'known to broke
> obscure userspace apps'.
True, but abusing EMBEDDED for "only do that if you know what you are
doing and if it breaks, you have to keep the pieces" is not good
either.
Some other places that seem to fall into the same category are
IPX_INTERN ("...This might break existing applications...") which is
neither EMBEDDED nor EXPERIMENTAL or RMW_INSNS ("...It is very likely
that this will cause serious problems on any Amiga...") that is
dependent on ADVANCED.
Anyway, perhaps I should just select EMBEDDED although I don't have a
small system (though a 6 year old 1Ghz K7 with 1GB mem might be
considered small by some people these days :-), and ignore all the other
options that pop up through this.
Best,
Norbert
next prev parent reply other threads:[~2006-12-14 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 11:42 Norbert Kiesel
2006-12-06 11:58 ` Arjan van de Ven
2006-12-06 12:19 ` Norbert Kiesel
2006-12-06 12:45 ` Arjan van de Ven
2006-12-06 13:36 ` Norbert Kiesel
2006-12-06 21:00 ` Jan Engelhardt
2006-12-06 21:10 ` Jan Engelhardt
2006-12-06 13:10 ` Adrian Bunk
2006-12-09 12:27 ` Alejandro Riveira Fernández
2006-12-09 15:45 ` Norbert Kiesel
2006-12-09 16:01 ` Adrian Bunk
2006-12-14 14:47 ` Pavel Machek
2006-12-14 15:24 ` Norbert Kiesel [this message]
2006-12-10 4:26 linux
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=1166109884.8815.157.camel@titan.tbdnetworks.com \
--to=nkiesel@tbdnetworks.com \
--cc=ariveira@gmail.com \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®