All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Vladimir Dergachev <volodya@mindspring.com>
Cc: Jon Smirl <jonsmirl@gmail.com>, Dave Airlie <airlied@linux.ie>,
	DRI Devel <dri-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Merging DRM and fbdev
Date: Sun, 03 Oct 2004 23:19:24 +0100	[thread overview]
Message-ID: <1096841964.16457.17.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0410031145560.17248@node2.an-vo.com>

On Sul, 2004-10-03 at 16:50, Vladimir Dergachev wrote:
> In particular, I can contribute the code that does Framebuffer->System Ram
> transfers over PCI/AGP. It is currently GPL licensed, but there is no 
> problem if BSD folks want it too.

This will do *wonders* to X render performance if used properly on those
cards we can't do render in hardware.

> This is also potentially useful for any Mesa functions that want to 
> transfer data back from video RAM - using plain reads for this is really slow.

Agreed - and Mesa tends to skip even tricks like SSE2 that can quadruple
read performance.

  parent reply	other threads:[~2004-10-03 23:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-03  3:55 Merging DRM and fbdev Jon Smirl
2004-10-03  7:26 ` Dave Airlie
2004-10-03 15:33   ` Jon Smirl
2004-10-03 15:50     ` Vladimir Dergachev
2004-10-03 16:24       ` Jon Smirl
2004-10-03 16:59         ` Vladimir Dergachev
2004-10-03 17:55           ` Jon Smirl
2004-10-03 20:37             ` Vladimir Dergachev
2004-10-03 22:42               ` Jon Smirl
2004-10-03 22:16                 ` Alan Cox
2004-10-03 22:19       ` Alan Cox [this message]
2004-10-04  1:56         ` Vladimir Dergachev
2004-10-03 18:38     ` Mike Mestnik
2004-10-03 18:56       ` Jon Smirl
2004-10-04 19:48         ` Bill Davidsen
2004-10-03 16:46   ` Jon Smirl
2004-10-04 17:47     ` Tonnerre
2004-10-04 18:42       ` Jon Smirl

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=1096841964.16457.17.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=volodya@mindspring.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.