Bug 2491

Summary: RFE: Unify libint10 on x86
Product: xorg Reporter: Mike A. Harris <mharris>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: lowest CC: eich, jcristau, roland.mainz
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
kaouete's dmesg (see mtrr errors maybe)
none
xorg logs (see vm86 error) none

Description Mike A. Harris 2005-02-07 17:26:27 UTC 
On x86 arch, 2 copies of libint10 are supplied, one using vm86, and the
other using x86emu.  It would be a nice feature enhancement for someone
to unify the two into a single module for the future, which defaults to
using vm86, but can fall back to using x86emu if vm86 fails or is overridden
via config file or commandline options.

I figured it was worth logging this in bugzilla as an enhancement request
for the future.  I haven't investigated what is needed to do this, or how
feasible it would be, but that can be discussed here.
Comment 1 Victor NOEL 2005-03-14 09:43:15 UTC 
Created attachment 2102 [details]
kaouete's dmesg (see mtrr errors maybe)
Comment 2 Victor NOEL 2005-03-14 09:43:51 UTC 
Created attachment 2103 [details]
xorg logs (see vm86 error)
Comment 3 Victor NOEL 2005-03-14 09:45:18 UTC 
arg, i dont know why but bugzilla added my file to this bug, i'm sorry for the
trouble.
Comment 4 Mike A. Harris 2006-08-31 07:18:51 UTC 
If I'm not mistaken, 7.1 already does this essentially.
Comment 5 Julien Cristau 2007-02-05 08:14:19 UTC 
(In reply to comment #4)
> If I'm not mistaken, 7.1 already does this essentially.
> 
As far as I can see, configure sets either INT10_VM86 or INT10_X86EMU, which means that only one of these is built.  This means that if you build the vm86 code on x86, X won't work with a 64bit kernel.  Am I missing something, or should this be reopened?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.