Displaying 20 results from an estimated 8000 matches similar to: "No subject"
2009 Jun 14
3
Syncing to vblank for interlaced video modes
Hello,
I'll start by applauding your efforts to make an open source driver for nv hardware. I imagine it is a very difficult task trying to reverse engineer hardware and produce something useful and featureful.
I wish to make a change to the nouveau source. You might say I am considering becoming a nouveau developer. I am one of those crazy nutters who connects my nvidia card directly to
2016 Mar 11
0
[ANNOUNCE] xorg-server 1.18.2
A big pile of updates in this one. Highlights include:
- glamor is updated to use OpenGL core profiles if available, which
should improve memory usage and performance on modern hardware, and got
some other performance improvements for rpi and other GLES platforms
- DRI2, DRI3, and Present all received correctness fixes for hangs,
crashes, and other weirdness
- Xwayland server has been updated
2013 Jun 30
0
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
On 29/06/13 21:21, Ilia Mirkin wrote:
> On Sat, Jun 29, 2013 at 2:07 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> Hi Ilia,
>>
>> On 27/06/13 12:26, Ilia Mirkin wrote:
>>> Adds H.264 and MPEG2 codec support via VP2, using firmware from the
>>> blob. Acceleration is supported at the bitstream level for H.264 and
>>> IDCT level for
2013 Jun 29
0
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
Hi Ilia,
On 27/06/13 12:26, Ilia Mirkin wrote:
> Adds H.264 and MPEG2 codec support via VP2, using firmware from the
> blob. Acceleration is supported at the bitstream level for H.264 and
> IDCT level for MPEG2.
>
> Known issues:
> - H.264 interlaced doesn't render properly
> - H.264 shows very occasional artifacts on a small fraction of videos
> - MPEG2 + VDPAU
2014 Sep 03
0
[ANNOUNCE] xf86-video-nouveau 1.0.11
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Highlights:
- Support for server managed fd's.
- Glamor support.
- Maxwell support.
- DRI3 and initial Present support.
- vsync'ed kms pageflip performance fixes when running on Linux 3.13+
- Multi-display vsync, vblank, swap scheduling, timestamping fixes.
- Multi x-screen support fixes.
- ZaphodHead support on for
2014 Sep 03
0
[ANNOUNCE] xf86-video-nouveau 1.0.11
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Highlights:
- Support for server managed fd's.
- Glamor support.
- Maxwell support.
- DRI3 and initial Present support.
- vsync'ed kms pageflip performance fixes when running on Linux 3.13+
- Multi-display vsync, vblank, swap scheduling, timestamping fixes.
- Multi x-screen support fixes.
- ZaphodHead support on for
2016 Sep 16
0
[ANNOUNCE] xorg-server 1.18.99.2
I think we're ready for RC1 at this point, but wanted to give people a
chance to scream about "just one more API change" until tomorrow. Let me
know if there's something I'm missing; if I don't hear anything, I'll be
tagging RC1 in the morning.
Aaron Plattner (1):
xace: Fix XaceCensorImage to actually censor the right part of the image
Adam Jackson (92):
2013 Jun 29
2
[PATCH] nv50: H.264/MPEG2 decoding support via VP2, available on NV84-NV96, NVA0
On Sat, Jun 29, 2013 at 2:07 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> Hi Ilia,
>
> On 27/06/13 12:26, Ilia Mirkin wrote:
>> Adds H.264 and MPEG2 codec support via VP2, using firmware from the
>> blob. Acceleration is supported at the bitstream level for H.264 and
>> IDCT level for MPEG2.
>>
>> Known issues:
>> - H.264 interlaced
2007 Jul 25
2
Using i915/i945 XvMc in Theora
Hi,
Intel has recently open sourced otion compensation code (XvMC) for
their i915/i945 integrated graphics chips.
See:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=blob;hb=xvmc-i915;f=src/xvmc/I915XvMC.c
XvMC API was intended for MPEG{2,4} class of codecs - so it can not be
used for Theora as-is. However, could at least some parts of it such as
hardware accelerated
2008 Jun 12
0
[ANNOUNCE] xf86-video-ati 6.8.191
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ati 6.9.0rc1 release
Lots of changes since the last release. Main things are
EXA composite support for r3xx/r4xx/r5xx chips and
textured video support on all radeons.
Adam Jackson (5):
Bump CRTC size limits on AVIVO chips so 30" displays work
without tweaking.
Add R500 unified shader register block.
Fix R500_US_CONFIG.
2020 Jan 15
0
[PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
The callback get_vblank_timestamp() is currently located in struct
drm_driver, but really belongs into struct drm_crtc_funcs. Add an
equivalent there. Driver will be converted in separate patches.
The default implementation is drm_calc_vbltimestamp_from_scanoutpos().
The patch adds drm_crtc_vblank_helper_get_vblank_timestamp(), which is
an implementation for the CRTC callback.
v2:
* rename
2020 Jan 16
0
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
Hi
Am 15.01.20 um 15:49 schrieb Ville Syrj?l?:
> On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote:
>> The callback get_vblank_timestamp() is currently located in struct
>> drm_driver, but really belongs into struct drm_crtc_funcs. Add an
>> equivalent there. Driver will be converted in separate patches.
>>
>> The default implementation is
2020 Jan 20
0
[PATCH v3 02/22] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
The new callback get_scanout_position() reads the current location
of the scanout process. The operation is currently located in struct
drm_driver, but really belongs to the CRTC. Drivers will be converted
in separate patches.
To help with the conversion, the timestamp calculation has been
moved from drm_calc_vbltimestamp_from_scanoutpos() to
2020 Jan 20
0
[PATCH v3 03/22] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
The callback get_vblank_timestamp() is currently located in struct
drm_driver, but really belongs into struct drm_crtc_funcs. Add an
equivalent there. Driver will be converted in separate patches.
The default implementation is drm_calc_vbltimestamp_from_scanoutpos().
The patch adds drm_crtc_vblank_helper_get_vblank_timestamp(), which is
an implementation for the CRTC callback.
v3:
* use
2020 Jan 23
0
[PATCH v4 02/22] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
The new callback get_scanout_position() reads the current location
of the scanout process. The operation is currently located in struct
drm_driver, but really belongs to the CRTC. Drivers will be converted
in separate patches.
To help with the conversion, the timestamp calculation has been
moved from drm_calc_vbltimestamp_from_scanoutpos() to
2020 Jan 20
0
[Intel-gfx] [PATCH v3 03/22] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
On Mon, Jan 20, 2020 at 09:22:55AM +0100, Thomas Zimmermann wrote:
> The callback get_vblank_timestamp() is currently located in struct
> drm_driver, but really belongs into struct drm_crtc_funcs. Add an
> equivalent there. Driver will be converted in separate patches.
>
> The default implementation is drm_calc_vbltimestamp_from_scanoutpos().
> The patch adds
2016 Jul 08
0
Help with nouveau driver
Thanks for the help so far, I have already solved the main problem,
but sadly it seems I can't find out the last step. I hope you can help
me there...
Here ist the important part: It is trying to load some nvidia module,
although i have already done apt-get purge nvidia*
[ 4.636] (II) LoadModule: "glx"
[ 4.638] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[
2020 Jan 15
2
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote:
> The callback get_vblank_timestamp() is currently located in struct
> drm_driver, but really belongs into struct drm_crtc_funcs. Add an
> equivalent there. Driver will be converted in separate patches.
>
> The default implementation is drm_calc_vbltimestamp_from_scanoutpos().
> The patch adds
2020 Jan 10
0
[PATCH 01/23] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
The new callback get_scanout_position() reads the current location of
the scanout process. The operation is currentyl located in struct
drm_driver, but really belongs to the CRTC. Drivers will be converted
in separate patches.
Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
---
drivers/gpu/drm/drm_vblank.c | 24 ++++++++----
include/drm/drm_drv.h |
2020 Jan 10
0
[PATCH 01/23] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
On Fri, 10 Jan 2020, Thomas Zimmermann <tzimmermann at suse.de> wrote:
> The new callback get_scanout_position() reads the current location of
> the scanout process. The operation is currentyl located in struct
> drm_driver, but really belongs to the CRTC. Drivers will be converted
> in separate patches.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>