https://bugs.freedesktop.org/show_bug.cgi?id=99119
Bruce Cherniak changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
As the original patchstack is now about 300 patches, I have choosen to
squash the patches together into three different parts.
- renderonly library
A lightweight library to add basic infrastructure for renderonly
GPUs. With this library it is possible to run wayland or and other
kms egl apps
Changes from V1 -> V2:
- updated Copyright
- added $(top_srcdir)/src/gallium/winsys to include path (suggested by Emil)
- adapted driver to new renderonly API
Signed-off-by: Christian Gmeiner
---
configure.ac | 12 ++
src/gallium/Makefile.am
This a very lightweight library to add basic support for renderonly
GPUs. A kms gallium driver must specify how a renderonly_scanout
objects gets created. Also it must provide file handles to the used
kms device and the used gpu device.
This could look like:
struct renderonly ro = {
.create_for
From: Thierry Reding
If a device doesn't support rendering and support for PRIME isn't
enabled via the DRI_PRIME environment variable or dri.conf, attempt to
find a render node which can be used to offload rendering.
Signed-off-by: Thierry Reding
---
Along with platform and host1x bus support i
From: Thierry Reding
Allow USB devices to be used as output slaves for PRIME. Note that this
currently doesn't work on the X.Org server's built-in modesetting driver
because it requires glamor in order to expose the necessary capabilities
through RandR.
It should be possible to use this in order
From: Thierry Reding
ARM SoCs usually have their DRM/KMS devices on the platform bus, so add
support for this bus in order to allow use of the DRI_PRIME environment
variable with those devices.
While at it, also support the host1x bus, which is effectively the same
but uses an additional layer i
The specification section 9.4 says :
When an application attempts to create many pipelines in a single
command, it is possible that some subset may fail creation. In that
case, the corresponding entries in the pPipelines output array will
be filled with VK_NULL_HANDLE values. If any pi
On 12/23/2016 05:39 PM, Lionel Landwerlin wrote:
> The specification section 9.4 says :
>
>When an application attempts to create many pipelines in a single
>command, it is possible that some subset may fail creation. In that
>case, the corresponding entries in the pPipelines output ar
The specification section 9.4 says :
When an application attempts to create many pipelines in a single
command, it is possible that some subset may fail creation. In that
case, the corresponding entries in the pPipelines output array will
be filled with VK_NULL_HANDLE values. If any pi
The specification section 9.4 says :
When an application attempts to create many pipelines in a single
command, it is possible that some subset may fail creation. In that
case, the corresponding entries in the pPipelines output array will
be filled with VK_NULL_HANDLE values. If any pi
The specification section 9.4 says :
When an application attempts to create many pipelines in a single
command, it is possible that some subset may fail creation. In that
case, the corresponding entries in the pPipelines output array will
be filled with VK_NULL_HANDLE values. If any pi
Bah... It's definitely illegal. I had fix glslang myself. I have some NIR
reworks planned that would make this work "properly" but it's a bit more
complicated than this hack. That said, I'm very reluctant to fix app bugs
in our driver. There are a lot of ways apps can go wrong with Vulkan and
w
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Dec 22, 2016 at 11:54 PM, Jason Ekstrand wrote:
> This sequence shows up The Talos Principal, at least under Vulkan,
Not really important, except maybe when looking for patches affecting
the game, but I've noticed you keep calling it "Principal", while the
game is "The Talos Principle".
Hi,
Either this, or the other commit fixed segfault with vkreplay on DOTA2
Vulkan trace (segfault happened in trace before DOTA2 came to its main
menu).
- Eero
On 23.12.2016 00:10, Jason Ekstrand wrote:
pushed
On Thu, Dec 22, 2016 at 1:56 PM, Jason Ekstrand mailto:ja...@jlekstrand.
Looks good,
Reviewed-by: Eduardo Lima Mitev
thanks!
On 12/23/2016 01:14 AM, Jason Ekstrand wrote:
> In this case we were dying when we tried to do SHL addr sampler imm(8)
> because that puts an immediate in src0 of a two source instruction. This
> fixes 2704 of the new separate sampler Vulkan C
Reviewed-by: Bas Nieuwenhuizen
On Fri, Dec 23, 2016 at 7:43 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> doom was causing a printf about an illegal color, it was due the
> non-void returning -1, and the other function checking for 4,
> align these.
>
> Signed-off-by: Dave Airlie
> ---
> src
On Fri, Dec 23, 2016 at 6:42 AM, Dave Airlie wrote:
> From: Dave Airlie
>
> This was seen in doom shaders, so handle it properly.
I was trying to just change the type and keep a single load/store.
Turns out that has some issues indeed, and is not that helpful for
shared accesses anyway, as LLVM
Thanks for all your work on Nouveau and I look forward to your
contributions to radeonsi
On Thu, 22 Dec 2016 at 23:16 Samuel Pitoiset
wrote:
> Hello,
>
> This series makes use of the scheduling control code in order to improve
> the
> instruction pipelining on Maxwell GPUs.
>
> Starting with the
20 matches
Mail list logo
