Messages in this thread | | | Date | Mon, 13 Mar 2006 23:16:51 +0100 | From | Adrian Bunk <> | Subject | Re: [patch] Require VM86 with VESA framebuffer |
| |
On Mon, Mar 13, 2006 at 01:58:49PM -0800, Jesse Barnes wrote: > On Monday, March 13, 2006 9:01 am, Arjan van de Ven wrote: > > Chuck Ebbert wrote: > > > In-Reply-To: <1142261096.25773.19.camel@localhost.localdomain> > > > References: <1142261096.25773.19.camel@localhost.localdomain> > > > > > > On Mon, 13 Mar 2006 14:44:56 +0000, Alan Cox wrote: > > >> 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).
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.
> Jesse
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/
| |