linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilija Hadzic <ihadzic@research.bell-labs.com>
To: David Airlie <airlied@redhat.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [RFC] Virtual CRTCs (proposal + experimental code)
Date: Thu, 03 Nov 2011 18:00:24 +0000	[thread overview]
Message-ID: <Pine.GSO.4.62.1111031247310.7191@umail> (raw)
In-Reply-To: <e80977e3-0992-454e-8ee2-2944560d3b3d@zmail16.collab.prod.int.phx2.redhat.com>



On Thu, 3 Nov 2011, David Airlie wrote:

>
> Well the current plan I had for this was to do it in userspace, I don't think the kernel
> has any business doing it and I think for the simple USB case its fine but will fallover
> when you get to the non-trivial cases where some sort of acceleration is required to move
> pixels around. But in saying that its good you've done what something, and I'll try and spend
> some time reviewing it.
>

The reason I opted for doing this in kernel is that I wanted to confine 
all the changes to a relatively small set of modules. At first this was a 
pragmatic approach, because I live out of the mainstream development tree 
and I didn't want to turn my life into an ethernal 
merging/conflict-resolution activity.

However, a more fundamental reason for it is that I didn't want to be tied 
to X. I deal with some userland applications (that unfortunately I can't 
provide much detail of .... yet) that live directly on the top of libdrm.

So I set myself a goal of "full application transparency". Whatever is 
thrown at me, I wanted to be able to handle without having to touch any 
piece of application or library that the application relies on.

I think I have achieved this goal and really everything I tried just 
worked out of the box (with an exception of two bug fixes to ATI DDX
and Xorg, that are bugs with or without my work).

-- Ilija


  parent reply	other threads:[~2011-11-03 18:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 15:59 [RFC] Virtual CRTCs (proposal + experimental code) Ilija Hadzic
2011-11-03 17:21 ` Daniel Vetter
2011-11-03 17:27 ` David Airlie
2011-11-03 17:53   ` Alan Cox
2011-11-03 18:00   ` Ilija Hadzic [this message]
2011-11-07 12:58 ` Dave Airlie
2011-11-07 13:52   ` Ilija Hadzic
2011-11-23 11:48 ` Dave Airlie
2011-11-24  5:59   ` Ilija Hadzic
2011-11-24  8:52     ` Dave Airlie
2011-11-24 10:52       ` Daniel Vetter
2011-11-25  5:11         ` Ilija Hadzic
2011-11-24 12:58       ` Alan Cox
2011-11-24 13:48         ` Dave Airlie
2011-11-25  4:08       ` Ilija Hadzic

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=Pine.GSO.4.62.1111031247310.7191@umail \
    --to=ihadzic@research.bell-labs.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).