--=_courier-16326-1055194236-0001-2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
On Mon, 2003-06-09 at 14:18, Dave Jones wrote:
> Any reason to restrict it to a single stepping ?
> This means you have to upgrade memtest every time a new model
> is released, which seems a bit of a pain.
This is the patch I use, which seems to make sense, since I don't know
of any other steppings. No point in parameterising the code until you
have some parameters.
<b
--=_courier-16326-1055194236-0001-2
Content-Type: text/plain; name="memtest.patch"; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename=memtest.patch
===== init.c 1.2 vs edited =====
--- 1.2/init.c Mon Jun 9 14:25:40 2003
+++ edited/init.c Mon Jun 9 14:27:42 2003
@@ -403,16 +403,12 @@
l1_cache = cpu_id.cache_info[3];
l1_cache += cpu_id.cache_info[7];
case 15:
- switch (cpu_id.model) {
- case 5:
- cprint(LINE_CPU, 0, "AMD Opteron");
- off = 11;
- l1_cache = cpu_id.cache_info[3];
- l1_cache += cpu_id.cache_info[7];
- l2_cache = (cpu_id.cache_info[11] << 8);
- l2_cache += cpu_id.cache_info[10];
- break;
- }
+ cprint(LINE_CPU, 0, "AMD Opteron");
+ off = 11;
+ l1_cache = cpu_id.cache_info[3];
+ l1_cache += cpu_id.cache_info[7];
+ l2_cache = (cpu_id.cache_info[11] << 8);
+ l2_cache += cpu_id.cache_info[10];
}
break;
--=_courier-16326-1055194236-0001-2--