On October 13, 2018 19:50:00 "Keith Packard" wrote:
Jason Ekstrand writes:
Actually, I think anv is doing the right thing too. Now I have no idea why
Keith was having problems.
anv is happily returning a valid pointer and radv is not?
In any case, I've switched to using vkGetInstanceProc
Jason Ekstrand writes:
> Actually, I think anv is doing the right thing too. Now I have no idea why
> Keith was having problems.
anv is happily returning a valid pointer and radv is not?
In any case, I've switched to using vkGetInstanceProcAddr for the
VkPhysicalDevice function and it works fi
On Sat, Oct 13, 2018 at 11:27 AM Jason Ekstrand
wrote:
> On Sat, Oct 13, 2018 at 11:24 AM Bas Nieuwenhuizen <
> b...@basnieuwenhuizen.nl> wrote:
>
>> On Sat, Oct 13, 2018 at 6:12 PM Jason Ekstrand
>> wrote:
>> >
>> > On Sat, Oct 13, 2018 at 10:58 AM Bas Nieuwenhuizen <
>> b...@basnieuwenhuizen.n
On Sat, Oct 13, 2018 at 11:24 AM Bas Nieuwenhuizen
wrote:
> On Sat, Oct 13, 2018 at 6:12 PM Jason Ekstrand
> wrote:
> >
> > On Sat, Oct 13, 2018 at 10:58 AM Bas Nieuwenhuizen <
> b...@basnieuwenhuizen.nl> wrote:
> >>
> >> On Fri, Oct 12, 2018 at 10:38 PM Keith Packard
> wrote:
> >> >
> >> > Acc
On Sat, Oct 13, 2018 at 6:12 PM Jason Ekstrand wrote:
>
> On Sat, Oct 13, 2018 at 10:58 AM Bas Nieuwenhuizen
> wrote:
>>
>> On Fri, Oct 12, 2018 at 10:38 PM Keith Packard wrote:
>> >
>> > According to the Vulkan spec:
>> >
>> > "Vulkan 1.0 initially required all new physical-device-level extens
On Sat, Oct 13, 2018 at 10:58 AM Bas Nieuwenhuizen
wrote:
> On Fri, Oct 12, 2018 at 10:38 PM Keith Packard wrote:
> >
> > According to the Vulkan spec:
> >
> > "Vulkan 1.0 initially required all new physical-device-level extension
> > functionality to be structured within an instance extension.
On Fri, Oct 12, 2018 at 10:38 PM Keith Packard wrote:
>
> According to the Vulkan spec:
>
> "Vulkan 1.0 initially required all new physical-device-level extension
> functionality to be structured within an instance extension. In order
> to avoid using an instance extension, which often requires
According to the Vulkan spec:
"Vulkan 1.0 initially required all new physical-device-level extension
functionality to be structured within an instance extension. In order
to avoid using an instance extension, which often requires loader
support, physical-device-level extension functionality may