For a few weeks now I am working on implementing Vulkan for VideoCore 6 AKA
42 (using V3D/DRM). Don't hold you breath ;)
Currently I am trying to understand what is necessary or how to interact
with V3D. So I am looking at TransformFeedback because it interacts with
quite a few other parts of the
e to compile a new
libvulkanintel.so and start tracing with that
What do you think would be the better reference? RADV?
On Tue, 27 Aug 2019 at 00:51, Jason Ekstrand wrote:
> On Mon, Aug 26, 2019 at 6:43 AM Daniel Stone wrote:
>
>> Hi Andreas,
>>
>> On Sun, 25 Aug 2019 at 21:11, A
First off, thanks for git grep. Did not know that yet.
Second - both hits are the definition. I am searching for the declaration.
On Thu, 3 Oct 2019 at 16:38, Ilia Mirkin wrote:
> $ git grep CmdBeginTransformFeedback
> src/amd/vulkan/radv_cmd_buffer.c:void radv_CmdBeginTransformFeedbackEXT(
> sr
; {$BUILD_DIR?}/src/amd/vulkan/radv_entrypoints.h
> {$BUILD_DIR?}/src/intel/vulkan/anv_entrypoints.h
>
> generated using the entrypoints.py scripts in the corresponding source
> directories.
>
> On Thu, Oct 3, 2019 at 5:46 PM Andreas Bergmeier
> wrote:
> >
> > Fir
What I am fuzzy about is why in `src`, there is actually an include for
`gallium/include` and `gallium/auxiliary` (in `inc_common`). AFAIU this
forces most of mesa to sooner or later use Gallium code. It seems to stem
from the introduction of Intels Vulkan drivers.
On Sun, 6 Oct 2019 at 03:54, Rob
Thanks. Seems like my google foo was weak.
On Fri, 8 Nov 2019 at 22:57, Chris Forbes wrote:
> This is enforcing a hard requirement in the spec:
>
> 30.1. Feature Requirements
>
> All Vulkan graphics implementations must support the following features:
>
> * robustBufferAccess
>
>
> On Fri, Nov 8
The problem of data transfer costs is not new in Cloud environments. At
work we usually just opt for paying for it since dev time is scarser. For
private projects though, I opt for aggressive (remote) caching.
So you can setup a global cache in Google Cloud Storage and more local
caches wherever yo
