VRM(VRD) detection versus CPUID

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Fri, 2 Jul 2004, Jean Delvare wrote:

> We will have to find one. If none we have to pick an arbitrary number,
> much like was done for AMD. If possible, pick one which makes some sense
> and is not likely to be needed later (i.e. < 80).

And what about INTEL_VRM_10x I assigned 10 which is not good Idea it is
lower than 80. Should I do 100 ?

One more question about the architecture dispatcher. I think I cannot do
any runtime manager. Because I'm using struct cpuinfo_x86 *c = cpu_data;
And if the module insterted on PPC the symbol wont be there..

Defined as a preprocessor macro in:

    * include/asm-sh/processor.h, line 73
    * include/asm-um/processor-generic.h, line 140
    * include/asm-x86_64/processor.h, line 86
    * include/asm-sparc/cpudata.h, line 24
    * include/asm-i386/processor.h, line 93
    * include/asm-ia64/processor.h, line 194
    * include/asm-sparc64/cpudata.h, line 28

In attachment is what I have now. There is one stupid #ifdef.
Two hours left before I leave :)

Regards

Rudolf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cpuidvrm2.c
Type: text/x-csrc
Size: 2495 bytes
Desc: here
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20040702/aecca7d3/attachment.bin 


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux