Re: [PATCH] radeon/vdpau: don't report VDPAU for r300
On 13.10.2014 01:10, David Heidelberger wrote: VDPAU support has been removed for r300 as useless, but message in Xorg.log remained. (II) RADEON(0): [DRI2] VDPAU driver: r300 Remove this message to prevent confusion. I don't really see the problem with keeping it. Some people are arguing that Mesa should build r300 VDPAU again for VDPAU presentation support; in that case it would be nice if we didn't have to revert this change again. :) OTOH it might make sense to do this to prevent the message from being printed for r100 and r200, which will most likely never get any kind of VDPAU support. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: installing VDPAU on Fedora 20 ??
On 12.10.2014 21:10, sean darcy wrote: and X log has no reference to vdpau: # grep -i vdpau /var/log/Xorg.0.log # That most likely means the Xorg radeon driver failed to initialize hardware acceleration in general. Please provide the full Xorg.0.log file. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: installing VDPAU on Fedora 20 ??
On Mon, Oct 13, 2014 at 10:59 AM, sean darcy wrote: > On 10/13/2014 10:14 AM, Alex Deucher wrote: >> >> On Sun, Oct 12, 2014 at 8:10 AM, sean darcy wrote: >>> >>> On F20: >>> >>> mesa-vdpau-drivers-10.1.5-1.20140607.fc20.x86_64 >>> libvdpau-0.7-1.fc20.x86_64 >>> vdpauinfo-0.1-1.fc20.x86_64 >>> >>> /usr/lib64/vdpau/libvdpau_radeonsi.so.1 >>> /usr/lib64/vdpau/libvdpau_radeonsi.so.1.0.0 >>> >>> Xorg.0.log: RADEON(0): Chipset: "KAVERI" (ChipID = 0x1318) >>> >>> dmesg: >>> [drm] UVD initialized successfully. >>> ... >>> [drm] VCE initialized successfully. >>> >>> But >>> >>> export VDPAU_DRIVER=radeonsi; vdpauinfo >> >> >> You don't need to set the VDPAU_DRIVER env var. The ddx already >> passes the appropriate driver name via dri2 just like 3d. >> >> Alex >> >>> display: :0.0 screen: 0 >>> Error creating VDPAU device: 23 >>> >>> and X log has no reference to vdpau: >>> >>> # grep -i vdpau /var/log/Xorg.0.log >>> # >>> >>> What am I missing? >>> >>> sean >>> > > Thanks, but: > > # unset VDPAU_DRIVER > # vdpauinfo > display: :0.0 screen: 0 > Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object > file: No such file or directory > Error creating VDPAU device: 1 > > But in any case, what do I need to do to set up vdpau ? Or is it not > available on kaveri? It works fine on kaveri. I'm not entirely sure how RH packages vdpau for fedora. Make sure you install the mesa-vdpau-drivers package. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: installing VDPAU on Fedora 20 ??
On 10/13/2014 10:14 AM, Alex Deucher wrote: On Sun, Oct 12, 2014 at 8:10 AM, sean darcy wrote: On F20: mesa-vdpau-drivers-10.1.5-1.20140607.fc20.x86_64 libvdpau-0.7-1.fc20.x86_64 vdpauinfo-0.1-1.fc20.x86_64 /usr/lib64/vdpau/libvdpau_radeonsi.so.1 /usr/lib64/vdpau/libvdpau_radeonsi.so.1.0.0 Xorg.0.log: RADEON(0): Chipset: "KAVERI" (ChipID = 0x1318) dmesg: [drm] UVD initialized successfully. ... [drm] VCE initialized successfully. But export VDPAU_DRIVER=radeonsi; vdpauinfo You don't need to set the VDPAU_DRIVER env var. The ddx already passes the appropriate driver name via dri2 just like 3d. Alex display: :0.0 screen: 0 Error creating VDPAU device: 23 and X log has no reference to vdpau: # grep -i vdpau /var/log/Xorg.0.log # What am I missing? sean Thanks, but: # unset VDPAU_DRIVER # vdpauinfo display: :0.0 screen: 0 Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory Error creating VDPAU device: 1 But in any case, what do I need to do to set up vdpau ? Or is it not available on kaveri? sean ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: installing VDPAU on Fedora 20 ??
On Sun, Oct 12, 2014 at 8:10 AM, sean darcy wrote: > On F20: > > mesa-vdpau-drivers-10.1.5-1.20140607.fc20.x86_64 > libvdpau-0.7-1.fc20.x86_64 > vdpauinfo-0.1-1.fc20.x86_64 > > /usr/lib64/vdpau/libvdpau_radeonsi.so.1 > /usr/lib64/vdpau/libvdpau_radeonsi.so.1.0.0 > > Xorg.0.log: RADEON(0): Chipset: "KAVERI" (ChipID = 0x1318) > > dmesg: > [drm] UVD initialized successfully. > ... > [drm] VCE initialized successfully. > > But > > export VDPAU_DRIVER=radeonsi; vdpauinfo You don't need to set the VDPAU_DRIVER env var. The ddx already passes the appropriate driver name via dri2 just like 3d. Alex > display: :0.0 screen: 0 > Error creating VDPAU device: 23 > > and X log has no reference to vdpau: > > # grep -i vdpau /var/log/Xorg.0.log > # > > What am I missing? > > sean > > ___ > xorg-driver-ati mailing list > xorg-driver-ati@lists.x.org > http://lists.x.org/mailman/listinfo/xorg-driver-ati ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Stride of 800x600 framebuffer
> I am very new to DRM and radeon driver, There are many concepts of Linux > graphic system I haven't acquired.I am looking help for a question about drm > framebuffer, it might be very simple to you. Why is stride of 800x600 > framebuffer is 832*4=3328? Actually the number of pitch 832 is derive from The hardware has certain limitations you have to confrom to, this is one of them, the framebuffer is most likely tiled, so has alignment requirements for the tiles. Dave. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Stride of 800x600 framebuffer
Hi all,
I am very new to DRM and radeon driver, There are many concepts of Linux
graphic system I haven't acquired.I am looking help for a question about
drm framebuffer, it might be very simple to you. Why is stride of 800x600
framebuffer is 832*4=3328? Actually the number of pitch 832 is derive from
int radeon_align_pitch(struct radeon_device *rdev, int width, int bpp, bool
tiled)
{
int aligned = width;
int align_large = (ASIC_IS_AVIVO(rdev)) || tiled;
int pitch_mask = 0;
switch (bpp / 8) {
case 1:
pitch_mask = align_large ? 255 : 127;
break;
case 2:
pitch_mask = align_large ? 127 : 31;
break;
case 3:
case 4:
pitch_mask = align_large ? 63 : 15;
break;
}
aligned += pitch_mask;
aligned &= ~pitch_mask;
return aligned;
}
Why we have to align the pitch? I discover that if I write directly a
800*600 32bpp raw image to /dev/fb0, the image could not be correctly
rendered, since the pitch is 832 instead of 800, however
the virtualize_size sysfs gave me is 800,600, which is correct.
I am working on an AMD g-series eval board with kernel 3.16.3.
Thank you
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati
