Open Bug 627968 Opened 13 years ago Updated 2 years ago

Add Intel GMA 600 GPU to Intel GMA 500 Family D2D Blocklist

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect

Tracking

()

REOPENED

People

(Reporter: scoobidiver, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [platform-rel-Intel])

GMA 600 (device id: 4102) is a new graphics cards for netbook.
See: http://en.wikipedia.org/wiki/Intel_GMA#Specifications

Add it to the GMA 500 family to have HW acceleration available.
Thanks for the heads up.

Are these cards already in mass circulation? Do they give us a significant number of crashes? If yes, this would need to block.
> Are these cards already in mass circulation? Do they give us a significant
> number of crashes? If yes, this would need to block.
They are blocked because they didn't exist when the Intel compliance matrix was implemented.
I want to whitelist them as they are included in the GMA 500 family. I don't have any feedback of crashy GMA 500.
Blocks: 601079
Note that this is a device blacklist, not a device whitelist. New unknown devices are allowed by default, not blocked by default.
Per comment 3, I renamed the summary.
Summary: Add Intel GMA 600 card to D2D/D3D whitelist → Add Intel GMA 600 GPU to Intel GMA 500 Family D2D Blocklist
Do you have any reason to believe the intel GMA 600 devices should be blocked?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #5)
> Do you have any reason to believe the intel GMA 600 devices should be
> blocked?
The bug is for unblocking it in case it would have been blocked but it's not necessary based on comment 3.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
My bad. It should be blocked for versions older than 5.0.0.2026 on Windows 7, older than  7.14.10.1006 on Vista and older than 6.14.11.1018 on XP like GMA 500 GPUs. See https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#Intel_cards
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Whiteboard: [platform-rel-Intel]
platform-rel: --- → ?
platform-rel: ? → ---
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.