| commit | 96d1fcf8b5a3a9c66fddeaa9fb71e4e68ee2e08b | |
| author | Ben Skeggs <bskeggs@redhat.com> | |
| Wed, 20 Apr 2011 04:36:13 +0000 (20 14:36 +1000) | ||
| committer | Ben Skeggs <bskeggs@redhat.com> | |
| Mon, 16 May 2011 00:50:57 +0000 (16 10:50 +1000) | ||
| tree | 5725a2df3eacaee55f9da6ed6fccbba641105f4c | treesnapshot (tar.gz zip) |
| parent | bfb61f43b37158d432a1897bc2a4bbbd41215fae | commitdiff |
drm/nouveau/pm: translate ramcfg strap through ram restrict table
Hopefully this is how we're supposed to correctly handle when the RAMCFG
strap is above the number of entries in timing-related tables.
It's rather difficult to confirm without finding a configuration where
the ram restrict table doesn't map 8-15 back onto 0-7 anyway. There's
not a single vbios in the repo which is configured differently..
In any case, this is probably still better than potentially reading
outside of the bounds of various tables..
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Hopefully this is how we're supposed to correctly handle when the RAMCFG
strap is above the number of entries in timing-related tables.
It's rather difficult to confirm without finding a configuration where
the ram restrict table doesn't map 8-15 back onto 0-7 anyway. There's
not a single vbios in the repo which is configured differently..
In any case, this is probably still better than potentially reading
outside of the bounds of various tables..
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
| drivers/gpu/drm/nouveau/nouveau_perf.c | diffblobblamehistory |