summaryrefslogtreecommitdiffstats
path: root/lib/hweight.c
diff options
context:
space:
mode:
authorBen Skeggs <bskeggs@redhat.com>2011-04-20 14:36:13 +1000
committerBen Skeggs <bskeggs@redhat.com>2011-05-16 10:50:57 +1000
commit96d1fcf8b5a3a9c66fddeaa9fb71e4e68ee2e08b (patch)
tree5725a2df3eacaee55f9da6ed6fccbba641105f4c /lib/hweight.c
parentbfb61f43b37158d432a1897bc2a4bbbd41215fae (diff)
downloadop-kernel-dev-96d1fcf8b5a3a9c66fddeaa9fb71e4e68ee2e08b.zip
op-kernel-dev-96d1fcf8b5a3a9c66fddeaa9fb71e4e68ee2e08b.tar.gz
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>
Diffstat (limited to 'lib/hweight.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud