
Recherche avancée
Autres articles (100)
-
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
Les sons
15 mai 2013, par -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
Sur d’autres sites (14218)
-
hwcontext_vaapi : Use PRIME_2 memory type for modifiers.
7 décembre 2021, par Bas Nieuwenhuizenhwcontext_vaapi : Use PRIME_2 memory type for modifiers.
This way we can pass explicit modifiers in. Sometimes the
modifier matters for the number of memory planes that
libva accepts, in particular when dealing with
driver-compressed textures. Furthermore the driver might
not actually be able to determine the implicit modifier
if all the buffer-passing has used explicit modifier.
All these issues should be resolved by passing in the
modifier, and for that we switch to using the PRIME_2
memory type.Tested with experimental radeonsi patches for modifiers
and kmsgrab. Also tested with radeonsi without the
patches to double-check it works without PRIME_2 support.v2 :
Cache PRIME_2 support to avoid doing two calls every time on
libva drivers that do not support it.v3 :
Remove prime2_vas usage.Signed-off-by : Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
-
Revision 29071a418e : Fix invalid memory access on 2x downscale. The issue was discovered on bitstrea
9 septembre 2014, par Alexander VoronovChanged Paths :
Modify /vp9/common/vp9_reconinter.c
Fix invalid memory access on 2x downscale.The issue was discovered on bitstream with 2x vertical downscale. For
zero MVs, y_pad is set to 1 only when vertical convolution is
required. The original code assumes that for y_step_q4 == 32 we don’t
perform vertical convolution. But vp9_setup_scale_factors_for_frame()
sets convolve functions so that when x_step and y_step are both not
equal to 16, convolve in both directions is performed. And convolve()
unconditionally subtracts one stride from source pointer when calls
convolve_horiz(). This leads to invalid memory access.Change-Id : I882dfa6081a58e172b5ffa55842bfcd6727f10bf
-
hwcontext_vulkan : check for memory size before choosing type
24 novembre 2020, par Lynne