From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: Arvind R <arvino55@gmail.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Michael D Labriola <mlabriol@gdeb.com>,
xen-devel-bounces@lists.xensource.com
Subject: Re: Re: [Patch RFC] ttm: nouveau accelerated on Xen pv-ops kernel
Date: Wed, 23 Jun 2010 10:38:24 -0400 [thread overview]
Message-ID: <20100623143822.GA3559@phenom.dumpdata.com> (raw)
In-Reply-To: <4C220A3F.2010805@invisiblethingslab.com>
> >>> I rebased the branch and it is now devel/kms.fixes-0.3
> >>>
> >> Which stable branch have you rebased it for (.31, .32, .33?)?
> >
> > .32.
> >
> > and then I backported the DRM/TTM/KMS from 2.6.34 to be able to test the
> > nouveau driver.
> >>
> >> Have you tested it with some composting Window Manager (e.g. in KDE or
> >> Gnome with enables desktop effects)?
> >
> > Yes. I think so (isn't that the default thing?).
>
> No, both KDE and GNOME have composition disabled by default. On KDE, you
> need to go to Computer/System Settings/Desktop and then "Enable Desktop
> Eff3cts". You might need to click on the "Advanced" tab, and choose
> XRender instead of Open GL (and maybe also tick "Disable Functionality
> checks").
On my nouveau it just says: "Desktop effects required hardware 3D
support." I will try with the Radeon and Intel graphics stuff next week.
>
> > Played some tuxracer when testing it on Radeon and I think the i915,
>
> i915 is the Intel card, right? So, it's not served by the nouveau code,
> is it?
Right... I don't think I actually tested the XRender code then.
But I did test the OpenGL code on Radeon and the Intel chipsets that I
had.
>
> > so the OpenGL components worked OK.
>
> Hmmm, that's interesting. I think I never got Open GL working on
> nouveau, even on baremetal (I tested via KDE -- see above).
Right. That is expected as the 3D components are not in the nouveau driver
yet. Based on "http://nouveau.freedesktop.org/wiki/":
"Any 3-D functionality that might exist is still unsupported. Do not ask
for instructions to try it. But you can read GalliumHowto in case you
are brave enough."
>
> > I know that 3D don't work on the nouveau driver so hadn't
> > tried that.
> >
>
> No worries, 3D desktop effects are overrated ;) All I want is "Expose" :)
Based on this: http://en.wikipedia.org/wiki/Xlib and the little example
code that comes with it I Expose events do work with Xen dom0
with Xorg 1.8 and with the nouveau driver.
.. snip ..
> >> Finally, have you tested S3 sleep? (Has anybody actually got pvops0 .31
> >> or .32 support S3 sleep?).
> >
> > HA! Working on that and S5 right now. Jeremy mentioned he did get S3
> > working, but hadn't tried other modes. S5, S3, and S1 on my SuperMicro
> > XF8TN just don't work. Not sure if I have the Xen ACPI hypercalls
> > thought in the code base.
>
> What is the fundamental difference in S3 sleep support between pvops0
> vs. xenlinux, which seems to support S3 sleep quite well. At least the
> 2.6.34-xenlinux, the one from OpenSUSE? Or is it just the .34 kernel,
> that apparently is said to have lots of S3 sleep improvements?
<spreads his arms> Don't know yet. Jeremy just pinged me and said he got
on his laptop S3 to suspend working quite well.
next prev parent reply other threads:[~2010-06-23 14:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 13:21 [Patch RFC] nouveau accelerated on Xen pv-ops kernel Arvind R
[not found] ` <d799c4761003100521h663c82eepda85f3f0309828c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-11 11:02 ` [Patch RFC] ttm: " Pekka Paalanen
2010-03-12 5:27 ` Arvind R
2010-03-28 10:20 ` Joanna Rutkowska
2010-03-30 5:50 ` Arvind R
2010-03-12 12:45 ` Arvind R
2010-03-12 13:20 ` Michael D Labriola
2010-03-13 22:03 ` Joanna Rutkowska
2010-03-15 14:44 ` Michael D Labriola
2010-03-15 23:13 ` Jeremy Fitzhardinge
2010-03-16 7:18 ` Arvind R
2010-03-16 16:48 ` Michael D Labriola
2010-03-16 16:40 ` Michael D Labriola
2010-03-16 17:21 ` Konrad Rzeszutek Wilk
2010-03-16 19:39 ` Michael D Labriola
2010-03-16 19:41 ` Konrad Rzeszutek Wilk
2010-03-17 1:01 ` Konrad Rzeszutek Wilk
2010-03-18 6:09 ` Arvind R
2010-03-19 15:29 ` Michael D Labriola
2010-03-20 6:01 ` Arvind R
2010-03-22 21:14 ` Michael D Labriola
2010-03-23 6:21 ` Arvind R
2010-03-23 12:45 ` Michael D Labriola
2010-03-23 13:27 ` Michael D Labriola
2010-03-25 7:05 ` Arvind R
2010-03-25 7:18 ` Jeremy Fitzhardinge
2010-03-29 14:42 ` Michael D Labriola
2010-06-09 17:43 ` Konrad Rzeszutek Wilk
2010-06-09 18:39 ` Pasi Kärkkäinen
2010-06-09 19:31 ` Konrad Rzeszutek Wilk
2010-06-17 17:51 ` Konrad Rzeszutek Wilk
2010-06-22 22:32 ` Joanna Rutkowska
2010-06-23 12:54 ` Konrad Rzeszutek Wilk
2010-06-23 13:21 ` Joanna Rutkowska
2010-06-23 14:38 ` Konrad Rzeszutek Wilk [this message]
2010-06-23 15:08 ` Konrad Rzeszutek Wilk
2010-06-24 19:55 ` Pasi Kärkkäinen
2010-06-24 21:00 ` Konrad Rzeszutek Wilk
[not found] ` <d799c4761003120445h57ab1373m31eb0add242ef74c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-16 13:25 ` Thomas Hellstrom
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=20100623143822.GA3559@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=arvino55@gmail.com \
--cc=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--cc=mlabriol@gdeb.com \
--cc=xen-devel-bounces@lists.xensource.com \
--cc=xen-devel@lists.xensource.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 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).