[lkml]   [2006]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why is "Memory split" Kconfig option only for EMBEDDED?
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
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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-14 17:08    [W:0.036 / U:0.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site