diff options
author | Michael Ellerman <mpe@ellerman.id.au> | 2017-05-30 15:10:37 +1000 |
---|---|---|
committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2017-06-06 20:49:05 +1000 |
commit | 25897895a076471dc4566671fda5cf7d2a2c3379 (patch) | |
tree | ce086cdd7233cd279a47595638877b2a38113029 /hdata | |
parent | 5d919e412090951ae0139dc8b7f1223fba5ada79 (diff) | |
download | skiboot-25897895a076471dc4566671fda5cf7d2a2c3379.zip skiboot-25897895a076471dc4566671fda5cf7d2a2c3379.tar.gz skiboot-25897895a076471dc4566671fda5cf7d2a2c3379.tar.bz2 |
mambo: Make xscom claim to be DD 2.0
In the mambo tcl we set the CPU version to DD 2.0, because mambo is not
bug compatible with DD 1.
But in xscom_read_cfam_chipid() we have a hard coded value, to work
around the lack of the f000f register, which claims to be P9 DD 1.0.
This doesn't seem to cause crashes or anything, but at boot we do see:
[ 0.003893084,5] XSCOM: chip 0x0 at 0x1a0000000000 [P9N DD1.0]
So fix it to claim that the xscom is also DD 2.0 to match the CPU.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'hdata')
0 files changed, 0 insertions, 0 deletions