mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-23 22:00:13 +01:00
hk: assume largePoints always set
doesn't matter. this came from a Mesa audit around Vulkan features. Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37240>
This commit is contained in:
parent
6eac1cefd9
commit
162f07f80c
1 changed files with 0 additions and 9 deletions
|
|
@ -111,15 +111,6 @@ asahi_fill_vdm_command(struct hk_device *dev, struct hk_cs *cs,
|
||||||
c->vdm_ctrl_stream_base = cs->addr;
|
c->vdm_ctrl_stream_base = cs->addr;
|
||||||
|
|
||||||
agx_pack(&c->ppp_ctrl, CR_PPP_CONTROL, cfg) {
|
agx_pack(&c->ppp_ctrl, CR_PPP_CONTROL, cfg) {
|
||||||
/* If largePoints is not enabled, we optimize out point size writes so
|
|
||||||
* need to force points to have size 1.0 with this bit.
|
|
||||||
*
|
|
||||||
* If largePoints is enabled, we can't set this bit since our point size
|
|
||||||
* writes will get ignored.
|
|
||||||
*
|
|
||||||
* Yes, the hardware engineers messed this up. Dates back to IMG days.
|
|
||||||
*/
|
|
||||||
cfg.default_point_size = !dev->vk.enabled_features.largePoints;
|
|
||||||
cfg.enable_w_clamp = true;
|
cfg.enable_w_clamp = true;
|
||||||
cfg.fixed_point_format = 1;
|
cfg.fixed_point_format = 1;
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue