From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Antonino Daplas <adaplas@pol.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] Require VM86 with VESA framebuffer
Date: Tue, 14 Mar 2006 23:13:49 +0100 [thread overview]
Message-ID: <1142374429.3027.84.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060314215634.GA2269@elf.ucw.cz>
On Tue, 2006-03-14 at 22:56 +0100, Pavel Machek wrote:
> On Po 13-03-06 15:30:26, Arjan van de Ven wrote:
> > On Mon, 2006-03-13 at 09:13 -0500, Chuck Ebbert wrote:
> > > Force VM86 when VESA framebuffer is enabled and fix a typo
> > > in the VM86 config entry. If VM86 is disabled there will
> > > be problems when starting X using the VESA driver.
> >
> >
> > this sounds wrong.
> >
> > The kernel works fine; it's X that needs vm86.. (but it needs that
> > anyway).... but that's no reason to make one kernel option require
> > another....
>
> How does X solve it on x86-64? x86-64 has no vm86. I agree it is X
> that needs fixing.
X has a complete enough x86 emulator for this stuff. Some builds of X
don't use it on x86, but it works just fine; all other architectures
use it always anyway
next prev parent reply other threads:[~2006-03-14 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 14:13 Chuck Ebbert
2006-03-13 14:30 ` Arjan van de Ven
2006-03-14 21:56 ` Pavel Machek
2006-03-14 22:13 ` Arjan van de Ven [this message]
2006-03-13 14:44 ` Alan Cox
2006-03-13 16:55 Chuck Ebbert
2006-03-13 17:01 ` Arjan van de Ven
2006-03-13 21:58 ` Jesse Barnes
2006-03-13 22:16 ` Adrian Bunk
2006-03-14 1:26 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142374429.3027.84.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=76306.1226@compuserve.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®