Require VM86 with VESA framebuffer
In-Reply-To: <[email protected]>
References: <[email protected]>
Quoted 1 line · Alan Cox
VESA does not require VM86 so this change is completely wrong.
What is this all about then?
Begin quote ------------------------------------------------------------------
Date: 10 Mar 2006 11:23:18 GMT
From: Kenneth Parrish <[email protected]>
Subject: [2.6.16-rc5-git13] Xorg.log difference
To: [email protected]
Message-ID: <[email protected]>
i see this difference with 2.6.16-rc5-git13 kernel. more info on request -kp
5c5
< Current Operating System: Linux fret 2.6.16-rc5-git13 #2 Fri Mar 10 10:45:41 2006 i686
---
Quoted 1 line
Current Operating System: Linux fret 2.6.15.6 #1 Tue Mar 07 13:44:04 2006 i686
13c13
< (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 10 04:49:26 2006
---
Quoted 1 line
(==) Log file: "
/var/log/Xorg.0.log", Time: Fri Mar 10 05:02:35 2006
327,337c327,383
< (EE) ATI(0): unknown type(0xffffffff)=0xff
< (II) ATI(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 < (II) ATI(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 < (II) ATI(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 < (II) ATI(0): EIP=0x00001306, EFLAGS=0x00003200
< (II) ATI(0): code at 0x000c1306:
< fb fc 80 fc a0 0f 84 a6 3c 80 fc 4f 0f 84 c0 2d
< 1e 06 57 56 55 52 51 53 50 50 8a c4 32 e4 d1 e0
< (II) stack at 0x00001ffa:
< 00 06 00 00 00 32
< (II) ATI(0): VESA BIOS not detected
---
Quoted 8 lines
(II) ATI(0): VESA BIOS detected
(II) ATI(0): VESA VBE Version 2.0
(II) ATI(0): VESA VBE Total Mem: 4096 kB
(II) ATI(0): VESA VBE OEM: ATI MACH64
(II) ATI(0): VESA VBE OEM Software Rev: 1.0 (II) ATI(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) ATI(0): VESA VBE OEM Product: MACH64GT (II) ATI(0): VESA VBE OEM Product Rev: 01.00
End quote ------------------------------------------------------------------ Begin quote ------------------------------------------------------------------
Date: 11 Mar 2006 03:01:00 GMT
From: Kenneth Parrish <[email protected]>
Subject: Re: [2.6.16-rc5-git13] Xorg.log difference
To: [email protected]
Message-ID: <[email protected]>
-=> In article 10 Mar 06 17:20:10, Ingo Oeser wrote to All <=-
yo Ingo :)
[ mach64 rage 3d dual pci+agp1 vbe undetected x11-6.7.0-i586-4 ] [..]
IO> Did you disable vm86 support, too?
IO> # CONFIG_VM86 is not set
bet that's it - thank ya :)
End quote ------------------------------------------------------------------
Quoted 3 lines
Worse
still the x86-64 does not support VM86 so you have just crippled the x86-64 port unneccessarily.
Huh? I checked my working x86_64 .config and found this:
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
...
CONFIG_VM86=yso I assumed it was OK to force VM86.
Signature · 2 lines
Chuck "Penguins don't come from next door, they come from the Antarctic!"
Quoted 10 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
References: <[email protected]>Quoted 1 line · Alan Cox
VESA does not require VM86 so this change is completely wrong.
What is this all about then?
that is about X requiring it. Not about anything kernel related.
Quoted 10 lines · Arjan van de Ven
Quoted 7 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
References: <[email protected]>Quoted 1 line · Alan Cox
VESA does not require VM86 so this change is completely wrong.
What is this all about then?
that is about X requiring it. Not about anything kernel related.
And X doesn't actually require it, it's just that some builds of the X int10 and VBE libraries assume it's available. They can be configured to use an x86 emulator instead, and probably should be by default so that non-x86 systems have a better chance of working (code coverage and all that).
Jesse
Quoted 10 lines · Jesse Barnes
Quoted 9 lines · Arjan van de Ven
Quoted 7 lines · Chuck Ebbert
In-Reply-To: <[email protected]>
References: <[email protected]>Quoted 1 line · Alan Cox
VESA does not require VM86 so this change is completely wrong.
What is this all about then?
Quoted 7 lines
Quoted 1 line
that is about X requiring it. Not about anything kernel related.
And X doesn't actually require it, it's just that some builds of the X int10 and VBE libraries assume it's available. They can be configured to use an x86 emulator instead, and probably should be by default so that non-x86 systems have a better chance of working (code coverage and all that).
You can only disable CONFIG_VM86 if you have set CONFIG_EMBEDDED=y.
That's OK considering that CONFIG_EMBEDDED=y has the semantics:
Allow me to disable more options to save space no matter how much this can break since I do _really_ know what I'm doing when I'm enabling CONFIG_EMBEDDED.
Expecting working kernels when randomly toggling options that get available with CONFIG_EMBEDDED=y is simply silly.
Quoted 1 line
Jesse
cu
Adrian
Signature · 4 lines
"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 SeedQuoted 1 line · Adrian Bunk
You can only disable
CONFIG_VM86if you have setCONFIG_EMBEDDED=y.
Or are runnig under Xen or 32bit binaries on 64bit. Either way X can already handle this if properly configured.