From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Daniel Stone <daniel@fooishbar.org>
Subject: Re: [PATCH] Make XAA support optional
Date: Wed, 18 Jan 2012 12:27:49 +0000 [thread overview]
Message-ID: <aefc95$2t8snc@orsmga001.jf.intel.com> (raw)
In-Reply-To: <20120118120443.GC4002@phenom.ffwll.local>
On Wed, 18 Jan 2012 13:04:43 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Jan 18, 2012 at 10:37:24AM +0000, Chris Wilson wrote:
> > On Wed, 18 Jan 2012 14:45:51 +1100, Daniel Stone <daniel@fooishbar.org> wrote:
> > > Does what it says on the box.
> >
> > Danvet can you please test this on your elderly i810 box and make sure
> > we don't accidentally open the can of worms. Any sign of regressions?
>
> Why don't we just rip it out entirely? If a bored soul ever ports this
> driver to kms we likely just need to reimplement proper accel with sna, so
> I don't think there's much value.
If we did rip it out, what happens? The X server uses the vesa driver,
which is equivalent to i810 for modesetting, no 3d support, no overlays,
and no accelerated blits (which is dying anyway). Am I right in thinking
that after removal of XAA, the legacy i810 offers no more functionality
or performance than is available through VESA?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-18 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 3:45 [PATCH] Make XAA support optional Daniel Stone
2012-01-18 10:37 ` Chris Wilson
2012-01-18 12:04 ` Daniel Vetter
2012-01-18 12:27 ` Chris Wilson [this message]
2012-01-18 12:41 ` Daniel Vetter
2012-01-18 14:36 ` Eugeni Dodonov
2012-01-19 0:16 ` Kenneth Graunke
2012-01-19 17:22 ` Glen Gray
2012-01-19 17:25 ` Daniel Vetter
2012-01-19 17:49 ` Eugeni Dodonov
2012-01-20 9:40 ` Glen Gray
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='aefc95$2t8snc@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.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