patch from Christian Zuckschwerdt:
Hi,
On Fri, 15 Jun 2001, Mark D. Studebaker wrote:
> I looked at the patch and I see there are separate
> /proc entries for the 9 and 12 bit outputs.
> Why not just make the 12 bit output the only output using "temp"??
> I don't understand the need for all the new /proc entries,
> except perhaps for debugging inside #ifdef DEBUG.
> Would you or Jan be willing to develop a patch that way?
> I'm all for increased accuracy as a standard feature - why not?
Ok. I rewrote the patch to support standard (9bit) and enhanced (12bit)
accuracy via the "temp" entry. The "raw" interface is also gone.
There are some quirks needed for the sensors app. It seems that
prog/sensors/chips.c fixes the output to %+3.1f
Thats not good for 12bit mode which gives you 2 decimals and therefor
wrong scaling.
Precision is .062 with 12bit (4 decimal bits) instead of .5 with 9bit (1
decimal bit). That way 2 decimals seem a natural choice.
On the other hand I see no obvious reason not to fix decimals to 1...
I'm lost there -- suggestions anyone?
Another problem is that 12bit is slow and laggy. I don't recommend making
it the default mode.
cu.
:
Christian
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1145 7894878c-1315-0410-8ee3-d5d059ff63e0
> - Update, if necessary, the version number of `sensors'
> (edit prog/sensors/main.c and change the VERSION define)
> `cvs diff -r Vx-y-z prog/sensors' is your friend.
It seems that VERSION is now defined to LM_VERSION, so I removed this line
from the checklist.
> - Update if necessary, the version number of libsensors
I did a `cvs diff -r V2-5-5'. Looking at it, I see no interface changes,
but I do see new functionality. So I updated the library minor version.
The library version is now 1.2.0.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1129 7894878c-1315-0410-8ee3-d5d059ff63e0
Alpha architecture. I've made compilation contingent on
the machine being an Alpha because the driver needs kernel
include files that are in <asm-alpha>, not <asm>, unless
you are set up as an Alpha.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1109 7894878c-1315-0410-8ee3-d5d059ff63e0
instructions on how to use the BT869 driver with a PAL TV, an X windows
server, and kernel 2.4.4.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1083 7894878c-1315-0410-8ee3-d5d059ff63e0
to force_addr. It is now consistent with the bus PCI adapters
that support base address setting (piix4, i801, viapro).
Other benefit is that via686a_find can now return -ENODEV,
and module will fail to load when base address is not set and
parameter is not used.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1073 7894878c-1315-0410-8ee3-d5d059ff63e0
The temperature registers are in different places for the two
versions. Both versions unfortunately have the same PCI ID.
Apparently the temperature conversion formulas are different
for the two versions. Neither is yet implemented in the driver.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1070 7894878c-1315-0410-8ee3-d5d059ff63e0
address and program the base address in the 686a.
This is NOT a PCI force; the 3057 device must
be present in lspci.
Should work for Asus A7V/K7V boards which don't set the
base address (because they also have a as99127f on them!??).
Some rough edges remain, because
via686a_find() does not know there is a force; that only
is apparent to via686a_detect().
Notably, the driver will stay loaded even if the address is
uninitialized and there is no force; also, the driver complains
that a force is needed even when you give it one.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@999 7894878c-1315-0410-8ee3-d5d059ff63e0