>
> So I think we do have enough people interested in this and should be able
> to cobble together something that does The Right Thing.
>
We indeed have a non-trivial set of people interested in the same set of
problems and each of us has partial and maybe competing solution. I want
to make it
On Thu, 24 Nov 2011, Dave Airlie wrote:
> Okay so thats pretty much how I expected it to work, I don't think
> Virtual makes sense for a displaylink attached device though,
> again if you were using a real driver you would just re-use whatever
> output type it uses, though I'm not sure how well
On Thu, Nov 24, 2011 at 03:26:49AM +0800, Keith Packard wrote:
> On Wed, 23 Nov 2011 16:29:58 +0800, Wu Fengguang
> wrote:
>
> > What I need is a hot plug hook that knows whether the monitor is
> > plugged or removed, which is only possible if the hook is called
> > after ->detect().
>
> That
On Thu, Nov 24, 2011 at 12:58 PM, Alan Cox wrote:
>> The thing is this is how optimus works, the nvidia gpus have an engine
>> that you can program to move data from the nvidia tiled VRAM format to
>
> This is even more of a special case than DisplayLink ;-)
>
>> Probably a good idea to do some
> The thing is this is how optimus works, the nvidia gpus have an engine
> that you can program to move data from the nvidia tiled VRAM format to
This is even more of a special case than DisplayLink ;-)
> Probably a good idea to do some more research on intel/nvidia GPUs.
> With intel you can't
Hi,
I came across this code snippet at vmwgfx_kms.c:2000. The loop variable i is
never used and rects is checked again and again. Should it be something like
rects[i].x instead of rects->x? Thanks.
for (i = 0; i < arg->num_outputs; ++i) {
if (rects->x < 0 ||
On Thu, Nov 24, 2011 at 08:52:45AM +, Dave Airlie wrote:
> So the main problem with taking all this code on-board is it sort of
> solves (a), and (b) needs another bunch of work. Now I'd rather not
> solve 50% of the issue and have future userspace apps just think they
> can ignore the
On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote:
> On Wed, 23 Nov 2011, Markus Trippelsdorf wrote:
>
> > > FIX idr_layer_cache: Marking all objects used
> >
> > Yesterday I couldn't reproduce the issue at all. But today I've hit
> > exactly the same spot again. (CCing the drm list)
>
>
On Thu, Nov 24, 2011 at 5:59 AM, Ilija Hadzic
wrote:
>
>
> On Wed, 23 Nov 2011, Dave Airlie wrote:
>
>> So another question I have is how you would intend this to work from a
>> user POV, like how it would integrate with a desktop environment, X or
>> wayland, i.e. with little or no
are looking for. I recognize that it disrupts your current views/plans on
how this should be done, but I do want to work with you to find a suitable
middle ground that covers most of the possiblities.
In case you are looking at my code to follow the above-described
scenarios, please make sure
On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote:
On Wed, 23 Nov 2011, Markus Trippelsdorf wrote:
FIX idr_layer_cache: Marking all objects used
Yesterday I couldn't reproduce the issue at all. But today I've hit
exactly the same spot again. (CCing the drm list)
Well this is
On Thu, Nov 24, 2011 at 5:59 AM, Ilija Hadzic
ihad...@research.bell-labs.com wrote:
On Wed, 23 Nov 2011, Dave Airlie wrote:
So another question I have is how you would intend this to work from a
user POV, like how it would integrate with a desktop environment, X or
wayland, i.e. with little
On Thu, Nov 24, 2011 at 03:26:49AM +0800, Keith Packard wrote:
On Wed, 23 Nov 2011 16:29:58 +0800, Wu Fengguang fengguang...@intel.com
wrote:
What I need is a hot plug hook that knows whether the monitor is
plugged or removed, which is only possible if the hook is called
after
On Thu, Nov 24, 2011 at 08:52:45AM +, Dave Airlie wrote:
So the main problem with taking all this code on-board is it sort of
solves (a), and (b) needs another bunch of work. Now I'd rather not
solve 50% of the issue and have future userspace apps just think they
can ignore the problem. As
The thing is this is how optimus works, the nvidia gpus have an engine
that you can program to move data from the nvidia tiled VRAM format to
This is even more of a special case than DisplayLink ;-)
Probably a good idea to do some more research on intel/nvidia GPUs.
With intel you can't read
On Thu, Nov 24, 2011 at 12:58 PM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
The thing is this is how optimus works, the nvidia gpus have an engine
that you can program to move data from the nvidia tiled VRAM format to
This is even more of a special case than DisplayLink ;-)
Probably a good
On Thu, 24 Nov 2011, Dave Airlie wrote:
Okay so thats pretty much how I expected it to work, I don't think
Virtual makes sense for a displaylink attached device though,
again if you were using a real driver you would just re-use whatever
output type it uses, though I'm not sure how well that
So I think we do have enough people interested in this and should be able
to cobble together something that does The Right Thing.
We indeed have a non-trivial set of people interested in the same set of
problems and each of us has partial and maybe competing solution. I want
to make it
Hi,
I came across this code snippet at vmwgfx_kms.c:2000. The loop variable i is
never used and rects is checked again and again. Should it be something like
rects[i].x instead of rects-x? Thanks.
for (i = 0; i arg-num_outputs; ++i) {
if (rects-x 0 ||
19 matches
Mail list logo
