lkml.org 
[lkml]   [2004]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRFC: let x86_64 no longer define X86
I'd like to send a patch after 2.6.10 that removes the following from 
arch/x86_64/Kconfig:

config X86
bool
default y

Additionally, I'll also check all current X86 uses to prevent breakages.


Why?

X86 is _the_ symbol to identify the i386 architecture, but the x86_64
port hijacked it. Kernel-wise, x86_64 is mostly simply a new port like
e.g. ia64.


Where is the problem?

To say "X86", you currently have to write "(X86 && !X86_64)" in the
Kconfig file. This is not intuitive.

Why is e.g. CONFIG_LBD available on x86_64 and even enabled in
defconfig?


Isn't this an incompatible change?

Yes it is.
But according to the current development model, such changes are allowed
in 2.6 .

And if you want to support both older and more recent kernels, the
following dependencies will be correct both before and after this
change:
- (X86 && !X86_64)
- (X86 && X86_64)


cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:08    [W:0.218 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site