venus: minor refactor
Merge request reports
Activity
96 96 }; This file is generated from venus-protocol, right?
If so, any change to these files should happen in that repo, either in the input data files, or the scripts that generate them.
But if the file is generated, then it probably doesn't matter any changes that make it easier to modify, as they aren't expected to be modified directly.
Anything under the
src/venus/venus-protocol
directory with thevn_protocol_renderer_
prefix is output generated from thevn_protocol.py
script in venus-protocol.Since this file is generated, the indices will get updated when regenerating the protocol to add new extensions meaning both the
vkr_extension_table
andvk_info_extension
list are kept in sync (otherwise thats a bug ;)).vkr
just decides which extensions it wants enabled.In general, when adding a new extension you should update the scripts and have the newly generated files replace the ones in both the driver (mesa) and the renderer (virglrenderer) instead of modifying them.
Got it. I was editing the files by hand all along
Thanks!Edited by Igor Torrente
- Resolved by Igor Torrente
added 2 commits
- Resolved by Igor Torrente
- Resolved by Igor Torrente
added 2 commits
enabled an automatic merge when the pipeline for 482af27c succeeds