From: "Christian König" <deathsimple@vodafone.de>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: VDPAU tries to open wrong DRM device
Date: Fri, 01 Jun 2012 12:19:07 +0200 [thread overview]
Message-ID: <4FC8971B.5010902@vodafone.de> (raw)
In-Reply-To: <4FC894A9.9000401@snewbury.org.uk>
On 01.06.2012 12:08, Steven Newbury wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have two DRM devices, i965 onboard, and a Radeon in a docking station.
>
> Both devices are enabled in my Xorg server layout Screen0 is the i965,
> and Screen1, the Radeon.
>
> When I run vdpauinfo or try using mplayer -vo vdpau on the Radeon, I
> get the error:
>
> do_winsys_init: DRM version is 1.6.0 but this driver is only
> compatible with 2.3.x (kernel 2.6.34) or later.
>
> This is the version of the intel DRM driver!
>
> The i965 obviously doesn't do VDPAU, since it's a "classic" driver,
> it's DRI card0. DRI card1, the radeon, seems to be properly
> configured. DRI works fine.
>
> I would open a bug, but I'm not sure *where* the problem is...
The error message comes from the radeon winsys inside mesa, but I'm not
sure if that bug is really there or if DRI is messing up the cards somehow.
I would assign it to mesa initially, we could change it later on anyway.
Christian.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk/IlKkACgkQGcb56gMuC62jPACgkQE0G037ZVB3Da46QkA7Ytv+
> 1voAni7GbMTkcdhutMAnXoI/bapxtvha
> =mmHS
> -----END PGP SIGNATURE-----
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
prev parent reply other threads:[~2012-06-01 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 10:08 VDPAU tries to open wrong DRM device Steven Newbury
2012-06-01 10:19 ` Christian König [this message]
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=4FC8971B.5010902@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=steve@snewbury.org.uk \
/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.