From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@osdl.org>, Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Antonino Daplas <adaplas@pol.net>, Andi Kleen <ak@suse.de>
Subject: Re: [patch] Require VM86 with VESA framebuffer
Date: Mon, 13 Mar 2006 13:58:49 -0800 [thread overview]
Message-ID: <200603131358.50374.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <4415A586.1010404@linux.intel.com>
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).
Jesse
next prev parent reply other threads:[~2006-03-13 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 16:55 Chuck Ebbert
2006-03-13 17:01 ` Arjan van de Ven
2006-03-13 21:58 ` Jesse Barnes [this message]
2006-03-13 22:16 ` Adrian Bunk
2006-03-14 1:26 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
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
2006-03-13 14:44 ` 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=200603131358.50374.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=76306.1226@compuserve.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome