driver. Some are handled by the tveeprom driver, which doesn't create
the eeprom interface file. So we must really test for the eeprom file,
and not the device directory.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4167 7894878c-1315-0410-8ee3-d5d059ff63e0
driver. Some are handled by the tveeprom driver, which doesn't create
the eeprom interface file. So we must really test for the eeprom file,
and not the device directory.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4165 7894878c-1315-0410-8ee3-d5d059ff63e0
This is needed because parse-edid is typically installed in one of these
directories, even though any user can use it.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4126 7894878c-1315-0410-8ee3-d5d059ff63e0
script provides all the information "sensors" does for SPD eeproms, so
we're not so far from dropping eeprom support from sensors.
Code cleanups.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3306 7894878c-1315-0410-8ee3-d5d059ff63e0
Round up timing data.
Minor display adjustments.
Group cycle and access times, display the CAS value for each (SDRAM).
Refactor some bitfield tests into loops (SDRAM).
Display latencies and burst length on a single line (SDRAM).
Don't display manufacturing location when undefined.
Check that the manufacturing date is proper BCD, else fall back to
hexadecimal display.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3303 7894878c-1315-0410-8ee3-d5d059ff63e0
Improve decoding of the memory type, using a simple heuristic to
differenciate between Rambus and other types.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3247 7894878c-1315-0410-8ee3-d5d059ff63e0
(the eeprom driver can read 32-byte slices instead of the whole data).
Read 64-byte blocks, as this allows some code cleanups.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3242 7894878c-1315-0410-8ee3-d5d059ff63e0
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
Jean Delvare