sh: Handle SH-4 FPU variants with broken CVR values.
Usually we can look to the CVR to work out whether we have an FPU or not. Unfortunately not all parts comply with this, so just set the flag manually for all SH-4 parts and clear it on the only SH-4 that doesn't have one (SH4-501). Signed-off-by: Paul Mundt <lethal@linux-sh.org>
This commit is contained in:
parent
50dd3145a5
commit
bdc27300f5
|
@ -71,11 +71,11 @@ int __init detect_cpu_and_cache_system(void)
|
|||
boot_cpu_data.dcache.ways = 4;
|
||||
} else {
|
||||
/* And some SH-4 defaults.. */
|
||||
boot_cpu_data.flags |= CPU_HAS_PTEA;
|
||||
boot_cpu_data.flags |= CPU_HAS_PTEA | CPU_HAS_FPU;
|
||||
boot_cpu_data.family = CPU_FAMILY_SH4;
|
||||
}
|
||||
|
||||
/* FPU detection works for everyone */
|
||||
/* FPU detection works for almost everyone */
|
||||
if ((cvr & 0x20000000))
|
||||
boot_cpu_data.flags |= CPU_HAS_FPU;
|
||||
|
||||
|
@ -161,6 +161,7 @@ int __init detect_cpu_and_cache_system(void)
|
|||
break;
|
||||
case 0x700:
|
||||
boot_cpu_data.type = CPU_SH4_501;
|
||||
boot_cpu_data.flags &= ~CPU_HAS_FPU;
|
||||
boot_cpu_data.icache.ways = 2;
|
||||
boot_cpu_data.dcache.ways = 2;
|
||||
break;
|
||||
|
|
Loading…
Reference in a new issue