On 17/9/20 19:13, Jason Ekstrand wrote:
One more comment: Could you make a big WIP MR with the whole driver
to act as a pointer to the branch for now?
Here you are:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6766
Then it can be the thing
that gets merged once the stuff
FYI: I just opened this issue:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3534
On Thu, Sep 17, 2020 at 12:13 PM Jason Ekstrand wrote:
>
> One more comment: Could you make a big WIP MR with the whole driver
> to act as a pointer to the branch for now? Then it can be the thing
> that gets
One more comment: Could you make a big WIP MR with the whole driver
to act as a pointer to the branch for now? Then it can be the thing
that gets merged once the stuff in a and b land.
--Jason
On Thu, Sep 17, 2020 at 12:10 PM Jason Ekstrand wrote:
>
> Good work, all! I'm super-happy to see
Good work, all! I'm super-happy to see another Vulkan driver land in Mesa.
On Thu, Sep 17, 2020 at 8:52 AM apinheiro wrote:
> Our development branch is ~525 patches on top of master, categorized as
> follows:
>a) Patches that touch common Mesa infrastructure (NIR, Vulkan WSI, Meson,
>
Hi everybody,
As some of you already know, we have been working on a Vulkan driver
(v3dv) for the Broadcom V3D GPU present in the Raspberry Pi 4. So far we
have beenworking on a personal branch, rebasing regularly, and we would
like to start discussing about the process to merge the driver in
