diff options
| author | Ben Skeggs <bskeggs@redhat.com> | 2014-11-04 15:13:30 +1000 |
|---|---|---|
| committer | Ben Skeggs <bskeggs@redhat.com> | 2014-12-02 15:44:06 +1000 |
| commit | 15606cb466836c3ca28404ccdeea5515a7579bd2 (patch) | |
| tree | 00cc9a7354aa0764de97bd4290e8b6406f248c4e /tools/perf/scripts/python/syscall-counts.py | |
| parent | 1a72f2bd1e2e5e52de5f2f3e6f7876d6decc4caa (diff) | |
drm/nouveau/bios: translate ramcfg strap through M0203
A machine has been spotted where the ramcfg strap is "8", and the ramcfg
xlat table goes 0-7,0-7, resulting in us selecting config 0 for memory
items. On this particular system, config "8" is available and supposed
to be used. It appears that starting from GT21x (where Mv2 appears),
we're supposed to use the value in this table instead.
One concern here is that not all the places we currently use ramcfg xlat
are supposed to be treated the same now. The strap xlat table wasn't
removed from the vbios either, presumably for some kind of good reason.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions