libsensors: Kill procfs and sysctl support, part 2.

git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4473 7894878c-1315-0410-8ee3-d5d059ff63e0

BACKGROUND

@@ -14,9 +14,8 @@ few general-purpose base kernel modules, which you always need. In
 addition, there is one kernel module for each piece of hardware - whether
 this is an I2C bus adapter, an SMBus adapter or a sensors chip.
 
-The kernel modules communicate their information through both the /proc
-and sysctl interfaces (Linux 2.4) or the /sys interface (Linux 2.6). To
-keep things uncomplicated, the sensor chips always advert their
+The kernel modules communicate their information through the /sys inter-
+face. To keep things uncomplicated, the sensor chips always advert their
 measurements 'as is'. This means that the values they report are not
 immediately relevant to you - they must first be scaled and translated
 to correspond to the real world.
@@ -31,7 +30,7 @@ This is important, because bugs in kernel-space might crash your
 computer or do other bad things. And kernel memory can not be swapped out!
 
 Applications could (and can) directly read the sensor values through the 
-/proc, sysctl or /sys interfaces. This is harder than it sounds; because
+/sys interface. This is harder than it sounds; because
 no two chips are the same, the information they communicate may also
 be very unlike. This would mean that every application would have to know
 about every type of chip. But there is a better solution.

CHANGES

@@ -14,7 +14,7 @@ SVN HEAD
            Add dme1737 support
            Delete support of non-sensor drivers (ddcmon, eeprom)
            Always build with sysfs support
-           Delete procfs support (Linux 2.4)
+           Delete procfs and sysctl support (Linux 2.4)
            Delete all remnants of algorithm names
   Man page sensors.conf.5: Update the chip statement section
   Programs doc/*: Delete, obsolete

lib/data.h

@@ -120,7 +120,6 @@ typedef struct sensors_bus {
 
 /* /proc/sys/dev/sensors/chips line representation */
 typedef struct sensors_proc_chips_entry {
-  int sysctl;
   sensors_chip_name name;
 } sensors_proc_chips_entry;
 
@@ -139,20 +138,12 @@ typedef struct sensors_proc_chips_entry {
    mode is SENSORS_MODE_NO_RW, SENSORS_MODE_R, SENSORS_MODE_W or
      SENSORS_MODE_RW, for unaccessible, readable, writable, and both readable
      and writable.
-   sysctl is the SYSCTL id of the file the value can be found in.
-   offset is the (byte) offset of the place this feature can be found.
    scaling is the number of decimal points to scale by.
-     This scaling is performed on the raw sysctl value, NOT the value
-     seen in /proc. Therefore the scaling value must be the same as
-     the value returned in nrels_mag by the SENSORS_PROC_REAL_INFO
-     operation in the chip drivers.
      Divide the read value by 10**scaling to get the real value.
      Scaling can be positive or negative but negative values aren't
      very useful because the driver can scale that direction itself. */
 typedef struct sensors_chip_feature {
   sensors_feature_data data;
-  int sysctl;
-  int offset;
   int scaling;
   const char *sysname;
   int sysscaling;