384.xx and libvulkan1 << 1.0.42 in stable?

[Luca Boccassi]

On Sat, 2017-11-04 at 01:51 +0100, Andreas Beckmann wrote:
> On 11/01/2017 02:17 PM, Luca Boccassi wrote:
> > On Wed, 2017-11-01 at 13:25 +0100, Andreas Beckmann wrote:
> > > if you have some time, could you test 375.82-7~bpo9+1 as prepared
> > > in
> 
> Something else that would be interesting to test for the 384.xx
> driver
> currently in experimental, is whether it works with the older
> libvulkan1
> in stable.
> 
> relevant changelog entries:
> 
>   * New upstream beta 381.09 (2017-04-06).
> 
>     - Added support for the following Vulkan extensions:
>       VK_EXT_acquire_xlib_display, VK_EXT_display_control,
>       VK_EXT_display_surface_counter, VK_EXT_direct_mode_display,
>       VK_KHX_external_memory, VK_KHX_external_memory_fd,
>       VK_KHX_external_semaphore, VK_KHX_external_semaphore_fd.
>       These extensions require a Vulkan loader version >= 1.0.42.
> 
>   * Bump libvulkan1 dependency to (>= 1.0.42).
> 
> stretch has 1.0.39.0+dfsg1-1
> 
> 
> Andreas
> 
> (that dependency got partially mismerged into 375.xx, will be dropped
> from there in the next upload)

Hi,

DOW3 works fine with 384.98 + libvulkan1 1.0.39. But I'm not sure if
it's using those new extensions - probably not.

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20171105/8996b6d8/attachment.sig>