Date: Thu, 18 Dec 2003 22:42:36 +0100
From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: sensors@Stimpy.netroedge.com
Subject: lm_sensors 2.8.2 / DESTDIR / root
The reason for this email is that I always try to avoid running
Makefiles as root, even during 'make install'. Therefore, I
always use the DESTDIR feature, when it's available. Until today,
I always built i2c and lm_sensors by doing
$ make
$ make -i install DESTDIR=/foo
$ cd /foo && su root && fix permissions/ownership && install
The -i flag to make install is a kludge to avoid having to be root
while installing to the DESTDIR, and it's only required because
the files are installed with "-o root -g root". Using the -i
flag is of course not a good idea, since more fatal errors can
easily fly by undetected.
Today, I upgraded to Linux 2.6.0, and tried a similar install
procedure for lm_sensors, except that the make target is now "user"
and the install target is "user_install". I now noticed that the
DESTDIR variable is not used everywhere in "user_install", so I
couldn't use the -i kludge anymore. Instead, I wrote a patch that
removes the "-o root -g root" arguments to install everywhere, and
I also tried to add DESTDIR to all files/directories installed.
(The patch only applies to lm_sensors, not i2c, since only
lm_sensors is required in Linux 2.6.0.)
There's really no reason to say -o root -g root anyway, since if you
do install directly with make install, you have to be logged in as
root, and then the files will get the right ownership by default.
Much of the point of installing to a temporary DESTDIR is that you
don't have to be root, and that you can prepare the installation
by hand. Fixing the ownership is trivial:
chown -R root.root $DESTDIR
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2189 7894878c-1315-0410-8ee3-d5d059ff63e0
Subject:
[PATCH] Re: SOLVED: Ticket #1409
Date:
Fri, 03 Oct 2003 16:48:32 +0200
From:
Bjørn Mork <bjorn@mork.no>
Organization:
m
To:
Mark Studebaker <mds@paradyne.com>
CC:
lm78@stimpy.netroedge.com, LM_Sensors developers <sensors@stimpy.netroedge.com>
References:
1 , 2 , 3
Bjørn Mork <bjorn@mork.no> writes:
> Mark Studebaker <mds@paradyne.com> writes:
>
>> If you port over the super i/o code from one of the 3 drivers listed
>> above
>> and send us a patch we'll include it.
>
> OK. Will do.
Here's the patch as promised. Took the code from smsc47m1.c. It
currently only changes behaviour for the IT8712F since I cannot test
on any other IT87-chips, and the comments in sensors-detect made me
uncertain whether they really use the same key/exit sequence.
Also changed sensors-detect somewhat to support longer devids and exit
sequences. Don't know if you'll approve my perl though...
Bjørn
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2170 7894878c-1315-0410-8ee3-d5d059ff63e0
chip, but we'll guess that GPIO5 are used for this purpose. It's
correct for (at least) Asus P4C800-E, and if it's wrong for any
others then we're no worse off. Also, switch to using common LM75
conversion functions.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2151 7894878c-1315-0410-8ee3-d5d059ff63e0
header and gave them the prefix LM75_. Also rewrote them according
to the lm75 datasheet. The next step is to replace all the various
scattered (broken?) copies of these functions (especially in Winbond
subclients) with this one.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2130 7894878c-1315-0410-8ee3-d5d059ff63e0
Michael Hufer <michael.hufer@freenet.de>
------------------------
> First, I added a new mod parameter "reset_it87" which controls whether
> or not the chip is reset on module load (modprobe it87 reset_it=1,
> default) or not(modprobe it87 reset_it87=0).
> Since this worked out quiet nicely I decided to go one step further
> and also add the chips manual and automatic temperature controlled fan
> speed features (PWM etc.).
>
> Finally I also updated the doc to document the new features.
>
> Attached is a diff against the current cvs version.
------------------------
Subject:
Re: fan speed for it87?? chips added
Date:
Fri, 26 Sep 2003 23:28:35 +0200
From:
Michael Hufer <michael.hufer@freenet.de>
To:
sensors@Stimpy.netroedge.com, Jean Delvare <khali@linux-fr.org>
On Friday 26 September 2003 22:40, Jean Delvare wrote:
> > I found and fixed the little problem I had with the original chip
> > initialization. I can now load the module with reset_it87=0 and
> > init=1 without messing up the settings of the power supply fan
> > from the BIOS. It was quite simple after all.
>
> I'm interested in details, can you tell us what it was?
Sure, it actually was something I introduced myself :-(. I initialized the
fan_ctl register with (read_value & 0x8f | 0x77) to enable the smart
guardian feature for all 3 fans. But the power supply fan does not support
pwm. It can only be operated in on/off mode, i.e. bit 0 must be clear. I
switched it back to the original (rv & 0x8f | 0x70 ) and everything is back
to working.
> > Do you want me to send the latest diff?
>
> Sure I want.
Here it comes.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2033 7894878c-1315-0410-8ee3-d5d059ff63e0
- fix voltage scaling
- swap voltage limits
- use lower critical rather than upper hysteresis
for non-temperature sensors
- increase libsensors support to 20 voltage, 10 fan,
10 temperature sensors
Tickets 1406 and 1407.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2017 7894878c-1315-0410-8ee3-d5d059ff63e0
From:
Kalev Soikonen <sokos@starman.ee>
Hi.
I am using lm_sensors in a slightly patched form.
The motherboard is Intel D845BGL, which features
SMSC LPC47M142 LPC Bus I/O controller.
If you look at the 47m10x and 47m14x datasheets,
you'll notice they have different Device ID's
(the former has 0x59, the latter 0x5F). As far
as the fan monitoring is concerned, they are
pretty much identical.
The 47M142 will be recognized with only some
trivial modifications to the code. I've attached
diffs for lm_sensors-2.7.0 and lm_sensors-2.8.0.
Best regards,
Kalev Soikonen
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1993 7894878c-1315-0410-8ee3-d5d059ff63e0
Jean Delvare