Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 39

Thread: DRI2 Sync & Swap For ATI Finally Comes About

  1. #11
    Join Date
    Nov 2009
    Posts
    45

    Default

    Anyone knows if this impacts Qt environments like KDE (and Kwin) in any way?

  2. #12
    Join Date
    Dec 2007
    Posts
    248

    Default

    Quote Originally Posted by Neuro View Post
    Anyone knows if this impacts Qt environments like KDE (and Kwin) in any way?
    Good question ... The recent trend to mention Gnome techs while talking about Xorg (like Gstreamer X work) makes me wonder if any X devs are using/care about KDE at all.

    but maybe it's just because phoronix is biased towards Gnome

  3. #13
    Join Date
    Dec 2007
    Posts
    137

    Default

    Quote Originally Posted by val-gaav View Post
    Have you tried turning off KMS and using UMS instead ?
    Been there. Totem becomes unstable and Parole is too lacking in core functionality (plus I can't seem to get it to build on 10.04, for some reason), to replace it. With the sole exception of gstreamer failing to downmix AAC audio with ALSA (oddly enough, it works with pulse, even when pulse is merely acting as a wrapper for ALSA), gstreamer has been the only multimedia backend that's worked reliably for me. Mplayer and VLC both have performance difficulties, with motion jidders, regardless of DRI2 redirected overlays.

    Quote Originally Posted by Neuro View Post
    Anyone knows if this impacts Qt environments like KDE (and Kwin) in any way?
    Of course. What made you think this was Gtk/Gnome related? The article is about the KMS and DDX driver work.

    Quote Originally Posted by val-gaav View Post
    Good question ... The recent trend to mention Gnome techs while talking about Xorg (like Gstreamer X work)
    I hope that's not to imply gstreamer is, "Gnome tech".

  4. #14
    Join Date
    Oct 2008
    Posts
    50

    Default

    Anybody knows if the patch for the kernel-module is already merged to the drm-radeon-testing branch? And if not where i can find it?

  5. #15
    Join Date
    Nov 2009
    Posts
    45

    Default

    Quote Originally Posted by etnlWings View Post
    Of course. What made you think this was Gtk/Gnome related? The article is about the KMS and DDX driver work.
    Not really. It seems that it's a non-standard GLX operation: A new GLX swap event extension also came about out of expressed needs by the Clutter/Mutter developers.. Thus, I wonder if KWin composite manager can use it and if Qt can use it in it's opengl renderer (as opposed to the software renderer).

    I hope that's not to imply gstreamer is, "Gnome tech".
    Well, it's Glib tech Gnome is the major user of Glib and AFAIK Gnomes main player Totem uses GStreamer (correct me if I'm wrong), so they're tightly related.

  6. #16
    Join Date
    Dec 2007
    Posts
    137

    Default

    Quote Originally Posted by Neuro View Post
    Not really. It seems that it's a non-standard GLX operation: A new GLX swap event extension also came about out of expressed needs by the Clutter/Mutter developers.. Thus, I wonder if KWin composite manager can use it and if Qt can use it in it's opengl renderer (as opposed to the software renderer).
    Oh, I misinterpreted your question. Sorry. It's just a matter of implementation, I suppose.

    Well, it's Glib tech Gnome is the major user of Glib and AFAIK Gnomes main player Totem uses GStreamer (correct me if I'm wrong), so they're tightly related.
    Glib's been it's own entity for a while now and yes totem uses gstreamer but it can (could?) also use xine. Gstreamer's not exactly a project that emerged within the Gnome eco-sphere and it's also worth pointing out that phonon can use gstreamer and does so by default, IIRC - at least on the distributions I'm familiar with. During the KDE4.0 development cycle, it was the belle of the ball in Gnome, KDE and freedesktop.org's efforts to standardise a lot of the underlying implementation of common technologies.

  7. #17

    Default

    Quote Originally Posted by Neuro View Post
    Well, it's Glib tech Gnome is the major user of Glib and AFAIK Gnomes main player Totem uses GStreamer (correct me if I'm wrong), so they're tightly related.
    GStreamer is a default media engine it Qt. It works in KDE as a Phonon backend, but its implementation seems to be not perfect at this moment. It become more neutral in my opinion, but I prefer other engines.

  8. #18

    Default

    Quote Originally Posted by RealNC View Post
    Welcome to Linux where you can't update a single driver without updating them all. gg.
    Maybe such things like Sync&Swap are just already implemented in the Windows kernel and newer drivers bring only bugfixes and support for newer cards? To upgrade a single video driver afaik you don't have to use newer kernel.

  9. #19
    Join Date
    Nov 2009
    Posts
    45

    Default

    Quote Originally Posted by kraftman View Post
    Maybe such things like Sync&Swap are just already implemented in the Windows kernel and newer drivers bring only bugfixes and support for newer cards? To upgrade a single video driver afaik you don't have to use newer kernel.
    Actually under Linux you don't need a new kernel either. You could checkout drm testing and buidl the modules separately just like v4l. That of course would be impractical, but it is possible.

    As for Windows. Well, there you have the kernel which is provided by Microsoft and you've got the driver that's provided by AMD. The stack used by AMD is completely separate from the Microsoft kernel stack, apart from using the appropriate kernel APIs. Thanks to that, when the Microsoft API changes, you can say goodbye to your old driver and your old graphics card, it simply won't work.

    Both models have their strengths and weaknesses, so the above "single driver" rant isn't really worth taking note of.

  10. #20
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,281

    Default

    Windows and Linux hardware driver both include kernel and multiple userspace components. The only "difference" here is that Windows and Linux binary drivers deliver all the required components are delivered as a single bundle, while in the open source world each of the required components is a separate source tree (project).

    The components still have to be designed as a set, and during times of rapid change to internal APIs it's a good idea to upgrade them as a set.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •