Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Consume No OptionRom Policy in PciBusDxe #807

Closed
os-d opened this issue Apr 12, 2024 · 2 comments
Closed

[Feature]: Consume No OptionRom Policy in PciBusDxe #807

os-d opened this issue Apr 12, 2024 · 2 comments
Assignees
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:medium Important with a moderate impact

Comments

@os-d
Copy link
Contributor

os-d commented Apr 12, 2024

Feature Overview

Today there is an odd model of PciBusDxe calling into drivers that subscribe to a callback to determine if a given oprom should be loaded.

Solution Overview

PciBusDxe should consume a policy to decide what classes of oproms should be loaded. This should be an allow list. Furthermore, the policy should also contain a deny list of vendor ids and device ids to block loading those if required. This model allows the core to have control but a platform to configure the policy for their platform.

Alternatives Considered

No response

Urgency

Medium

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@os-d os-d added state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal labels Apr 12, 2024
@github-actions github-actions bot added state:needs-owner Needs an issue owner to be assigned urgency:medium Important with a moderate impact and removed state:needs-owner Needs an issue owner to be assigned labels Apr 12, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label May 27, 2024
Copy link

github-actions bot commented Jun 4, 2024

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:medium Important with a moderate impact
Projects
None yet
Development

No branches or pull requests

2 participants