Prev: Power management issue in NDIS/KMDF
Next: Why no "disable" option in device manager?
From: CPlusPlus on 16 Apr 2010 15:43
Hello,

I am interested in learning how to read SPD data stored in EEPROM of
memory modules, i.e, RAM. I am new to device driver development and
trying to locate good source of information to accomplish this task.
What methods are available to accomplish it via kernel level API
calls?

Thanks
From: Maxim S. Shatskih on 16 Apr 2010 15:58
I have doubts if this is ever possible for anybody except SMM BIOS, and surely this will change a lot from one memory controller chip to another. Try to find the detailed north bridge chip spec from Intel or nVidia.

Nobody except BIOS should see this.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

"CPlusPlus" <aamir.amna(a)live.com> wrote in message news:5d83c3e5-e3e9-42ae-afdd-16eb339cbb20(a)20g2000vbr.googlegroups.com...
> Hello,
>
> I am interested in learning how to read SPD data stored in EEPROM of
> memory modules, i.e, RAM. I am new to device driver development and
> trying to locate good source of information to accomplish this task.
> What methods are available to accomplish it via kernel level API
> calls?
>
> Thanks
From: Jeff Henkels on 16 Apr 2010 16:37
Well, the CPU-Z tool from http://www.cpuid.com does it, at least on every
modern system I've run it on. My guess is that it uses SMM BIOS, but I've
never really cared enough to dig into it.

The OP may find it worthwhile to play with the CPU-Z program to figure out
how they're accessing the SPD.

"Maxim S. Shatskih" <maxim(a)storagecraft.com.no.spam> wrote in message
news:OkpIy8Z3KHA.3728(a)TK2MSFTNGP06.phx.gbl...
I have doubts if this is ever possible for anybody except SMM BIOS, and
surely this will change a lot from one memory controller chip to another.
Try to find the detailed north bridge chip spec from Intel or nVidia.

Nobody except BIOS should see this.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

"CPlusPlus" <aamir.amna(a)live.com> wrote in message
news:5d83c3e5-e3e9-42ae-afdd-16eb339cbb20(a)20g2000vbr.googlegroups.com...
> Hello,
>
> I am interested in learning how to read SPD data stored in EEPROM of
> memory modules, i.e, RAM. I am new to device driver development and
> trying to locate good source of information to accomplish this task.
> What methods are available to accomplish it via kernel level API
> calls?
>
> Thanks


From: Maxim S. Shatskih on 16 Apr 2010 16:52
> The OP may find it worthwhile to play with the CPU-Z program to figure out
> how they're accessing the SPD.

Yes, I think they have several proprietary code paths for each chipset, just like the good old Motherboard Monitor.

Too bad the BIOS vendors do not define fans and temperature/voltage probes in their ACPI table properly, so that they will be accessible by WMI/VBScript.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: m on 16 Apr 2010 22:56
+1 - I have had the misfortune to have implemented SMBIOS and ACPI decode
logic in a couple of projects, but been very disappointed that even high-end
brand name HW (IE IBM, HP etc.) does not not reliably expose anything

"Maxim S. Shatskih" <maxim(a)storagecraft.com.no.spam> wrote in message
news:#OgNxaa3KHA.556(a)TK2MSFTNGP04.phx.gbl...
>> The OP may find it worthwhile to play with the CPU-Z program to figure
>> out
>> how they're accessing the SPD.
>
> Yes, I think they have several proprietary code paths for each chipset,
> just like the good old Motherboard Monitor.
>
> Too bad the BIOS vendors do not define fans and temperature/voltage probes
> in their ACPI table properly, so that they will be accessible by
> WMI/VBScript.
>
> --
> Maxim S. Shatskih
> Windows DDK MVP
> maxim(a)storagecraft.com
> http://www.storagecraft.com
>
 |  Next  |  Last
Pages: 1 2
Prev: Power management issue in NDIS/KMDF
Next: Why no "disable" option in device manager?