<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/09/14 18:10, "Thomas B. Rücker"
wrote:<br>
</div>
<blockquote cite="mid:541328EE.3090506@ruecker.fi" type="cite"> You
can run either a multi-arch distro or a 32-bit userland with a
64bit kernel.<br>
Unless you need to somehow plug some binary only 32bit kernel
module in, there should be no reason for a 32bit kernel, from what
I can tell.<br>
</blockquote>
<br>
config VM86<br>
bool "Enable VM86 support" if EXPERT<br>
default y<br>
<b>depends on X86_32</b><br>
---help---<br>
This option is required by programs like DOSEMU to run<br>
16-bit real mode legacy code on x86 processors. It also
may<br>
be needed by software like XFree86 to initialize some
video<br>
cards via BIOS. Disabling this option saves about 6K.<br>
<br>
It had been a while since I'd looked, so wasn't sure if this was
still the case after the X86 restructuring, but seems that it still
requires a 32 bit kernel to work.<br>
<br>
This isn't for any binary-only stuff or kernel modules, it's
standard userspace code. Sometimes there are alternatives,
sometimes not. What it's referring to with the XFree86 comment is
the need to run some code from rom on an add-in card. Legacy reasons
mean this is typically 16bit code. PC's have the advantage of being
quite standardised and very backward compatible, but that does come
with baggage like needing to be compatible with 1981.<br>
<br>
<br>
</body>
</html>