Skip to content

Conversation

@justxuewei
Copy link
Contributor

Rutabaga_gfx, since v0.1.75, supports specifying a GPU path (e.g.
/dev/dri/renderD128) for virglrenderer. This patch introduces a
--gpu-path argument to allow users to use any GPU they want.

Rutabaga_gfx, since v0.1.75, supports specifying a GPU path (e.g.
/dev/dri/renderD128) for virglrenderer. This patch introduces a
`--gpu-path` argument to allow users to use any GPU they want.

Signed-off-by: Xuewei Niu <[email protected]>
@justxuewei
Copy link
Contributor Author

@dorindabassey
Copy link
Collaborator

Hi Xuewei, Thanks for this PR! However, we have an ongoing refactoring effort that changes the architecture away from rutabaga_gfx to use the virglrenderer crate directly (see PR #890 ).
The good news is that this feature (GPU path specification) is already supported in virglrenderer and will be easier to implement in the new architecture. Once the refactoring PR is merged, we can:

  1. Add the --gpu-path argument to the CLI
  2. Pass it directly to virglrenderer's initialization

This will actually be more straightforward than the current approach since we'll be using the direct virglrenderer FFI bindings instead of going through rutabaga_gfx's additional abstraction layer.

@justxuewei
Copy link
Contributor Author

@dorindabassey Sounds good to me! Thanks for the very quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants