Skip to content

Conversation

@paul-court
Copy link
Contributor

@paul-court paul-court commented Dec 20, 2021

I have an AMD Radeon VII (vega20) series GPU which is identifying with a vendor string of "AMD".

This is not present in the X11GLFactory list of preQualificationFilter vendor names, so my system (and probably any other vega20 based cards under Linux) will always fall back to software rendering.

This adds the "amd" string to the preQualificationFilter list.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JDK-8279013: ES2Pipeline fails to detect AMD vega20 graphics card

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/698/head:pull/698
$ git checkout pull/698

Update a local copy of the PR:
$ git checkout pull/698
$ git pull https://git.openjdk.java.net/jfx pull/698/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 698

View PR using the GUI difftool:
$ git pr show -t 698

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/698.diff

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Dec 20, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 20, 2021

Hi @Gargoyle, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user gargoyle" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@paul-court
Copy link
Contributor Author

/signed

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Dec 20, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 20, 2021

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@paul-court
Copy link
Contributor Author

Just as a side note, I signed the OCA last year when I was doing some work with the Helidon project. I thought it was one OCA for all things Oracle?

@kevinrushforth
Copy link
Member

I thought it was one OCA for all things Oracle?

It is. There is a manual step to verify the connection between a user's GitHub account and their OCA, but it ordinarily happens quickly. Given that we are close to the holidays, there may be a longer delay than usual.

@paul-court
Copy link
Contributor Author

... I signed the OCA last year ...

Added some emphasis. Hope I get a year off for Christmas next year! ;-)

/signed

@paul-court
Copy link
Contributor Author

Hi. I'm just wondering if there is anything else I need to do for the OCA? It's been 4 weeks now, so even taking into account the holidays, I'm wondering if this request has fallen through the cracks?

Thanks

@johanvos
Copy link
Collaborator

I agree this would be a good and easy fix. Since there is an easy fallback to sw-rendering, this issue might impact more runtime environments than we are aware of.
@kevinrushforth is there anything we can do to check the OCA status?

@kevinrushforth
Copy link
Member

I'll check into this.

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Jan 25, 2022
@openjdk openjdk bot added the rfr Ready for review label Jan 25, 2022
@mlbridge
Copy link

mlbridge bot commented Jan 25, 2022

Webrevs

Copy link
Member

@kevinrushforth kevinrushforth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, too.

@openjdk
Copy link

openjdk bot commented Jan 25, 2022

⚠️ @Gargoyle the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout JDK-8279013
$ git commit -c user.name='Preferred Full Name' --allow-empty -m 'Update full name'
$ git push

@openjdk
Copy link

openjdk bot commented Jan 25, 2022

@Gargoyle This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8279013: ES2Pipeline fails to detect AMD vega20 graphics card

Reviewed-by: kcr

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 29 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@kevinrushforth) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready Ready to be integrated label Jan 25, 2022
@paul-court
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Ready to sponsor label Jan 25, 2022
@openjdk
Copy link

openjdk bot commented Jan 25, 2022

@Gargoyle
Your change (at version bec8652) is now ready to be sponsored by a Committer.

@kevinrushforth
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jan 26, 2022

Going to push as commit ae334c5.
Since your change was applied there have been 29 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jan 26, 2022
@openjdk openjdk bot closed this Jan 26, 2022
@openjdk openjdk bot removed ready Ready to be integrated rfr Ready for review sponsor Ready to sponsor labels Jan 26, 2022
@openjdk
Copy link

openjdk bot commented Jan 26, 2022

@kevinrushforth @Gargoyle Pushed as commit ae334c5.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

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

Labels

integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants