Skip to content

Review GPU model renames #207

Description

@openjck

The hardware.json file renames some GPU models from their low-level names to more human-readable names.

"renames": [
{
"from": "gen7.5-haswell-gt2",
"to": "Haswell (GT2)"
},
{
"from": "gen7-ivybridge-gt2",
"to": "Ivy Bridge (GT2)"
},
{
"from": "gen6-sandybridge-gt2",
"to": "Sandy Bridge (GT2)"
},
{
"from": "gen6-sandybridge-gt1",
"to": "Sandy Bridge (GT1)"
},
{
"from": "gen7-ivybridge-gt1",
"to": "Ivy Bridge (GT1)"
},
{
"from": "gen4.5-gma4500hd",
"to": "GMA 4500HD"
},
{
"from": "gen7-baytrail",
"to": "Bay Trail"
},
{
"from": "gen4.5-gma4500",
"to": "GMA 4500"
},
{
"from": "gen8-broadwell-gt2",
"to": "Broadwell (GT2)"
},
{
"from": "gen3-gma3100",
"to": "GMA 3100"
},
{
"from": "gen3-gma950",
"to": "GMA 950"
},
{
"from": "gen7.5-haswell-gt21",
"to": "Haswell (GT21)"
},
{
"from": "gen7-ivybridge-gt22",
"to": "Ivy Bridge (GT22)"
},
{
"from": "gen6-sandybridge-gt23",
"to": "Sandy Bridge (GT23)"
},
{
"from": "gen6-sandybridge-gt14",
"to": "Sandy Bridge (GT14)"
},
{
"from": "gen7-ivybridge-gt15",
"to": "Ivy Bridge (GT15)"
},
{
"from": "gen4.5-gma4500hd6",
"to": "GMA 4500HD 6"
},
{
"from": "gen7-baytrail8",
"to": "Bay Trail 8"
},
{
"from": "gen4.5-gma45009",
"to": "GMA 4500 9"
},
{
"from": "gen8-broadwell-gt210",
"to": "Broadwell (GT 210)"
},
{
"from": "gen3-gma310011",
"to": "GMA 310011"
},
{
"from": "EVERGREEN-PALM",
"to": "Evergreen (Palm)"
},
{
"from": "gen9-skylake-gt2",
"to": "Skylake (GT2)"
},
{
"from": "EVERGREEN-CEDAR",
"to": "Evergreen (Cedar)"
},
{
"from": "CAYMAN-ARUBA",
"to": "Cayman (Aruba)"
},
{
"from": "gen4-gma3500",
"to": "GMA 3500"
},
{
"from": "Tesla-GT218",
"to": "GeForce GT218"
},
{
"from": "NV40-C61",
"to": "GeForce NV40"
},
{
"from": "gen7.5-haswell-gt3",
"to": "Haswell (GT3)"
},
{
"from": "gen7.5-haswell-gt1",
"to": "Haswell (GT1)"
},
{
"from": "EVERGREEN-TURKS",
"to": "Evergreen (Turks)"
},
{
"from": "gen8-cherryview",
"to": "Cherry View"
},
{
"from": "gen9-kabylake-gt2",
"to": "Kaby Lake (GT2)"
},
{
"from": "gen8-broadwell-gt3",
"to": "Broadwell (GT3)"
},
{
"from": "gen5-ironlake",
"to": "Ironlake"
},
{
"from": "gen9-coffeelake-gt2",
"to": "Coffee Lake (GT2)"
},
{
"from": "gen9-kabylake-gt1.5",
"to": "Kaby Lake (GT1.5)"
}
],

I think the current renames are accurate, but it's hard to be certain. I never found good documentation which clearly maps low-level names to human-readable names.

Among other things, we should ensure that we are not renaming any low-level subsets to their human-readable supersets. For example, CIK-KABINI is part of AMD's Radeon HD 8000 series, but it's not the only chipset in that series, so it would seem that it would be inaccurate to rename CIK-KABINI to Radeon HD 8000. (We may want to leave the name CIK-KABINI as-is for that reason.) There may be other cases where we should leave the low-level names as-is.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions