Add a FAQ entry about the eeprom entries which sensors won't

display anymore.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3065 7894878c-1315-0410-8ee3-d5d059ff63e0

doc/FAQ

@@ -108,6 +108,7 @@ lm_sensors
   4.32 Problems on particular systems
   4.33 Problems on 2.6 kernels
     4.33.1 i2c-viapro and via686a
+    4.33.2 Where are my EEPROMs?
 5 How to Ask for Help
   5.1 What to send us when asking for help
   5.2 What to do if a module won't insert?
@@ -1246,6 +1247,25 @@ integrated sensors driver for VIA bridges). This caused the second
 loaded driver to silently fail working. So do not load both i2c-viapro
 and via686a together unless you have a recent kernel.
 
+4.33.2 Where are my EEPROMs?
+----------------------------
+
+The 2.6.14-rc1 kernel introduced the hwmon class, which groups all
+hardware monitoring drivers in a logical way. The goal was to help
+libsensors grab the relevant sensors information in /sys. In particular:
+   * libsensors will no more need to know about the underlying bus types
+     (I2C/SMBus, ISA or other);
+
+   * libsensors will no more list non-hardware monitoring chips.
+   This explains why EEPROMs are no more displayed by `sensors': they
+are no hardware monitoring chips. The medium term plan is to drop
+eeprom support for all Linux 2.6 kernels, as it didn't fit well in the
+library code in the first place.
+
+   Note that you can still obtain information about your EEPROMs by
+using the dedicated perl scripts in `prog/eeprom': `ddcmon',
+`decode-dimms.pl', `decode-edid.pl' and `decode-vaio.pl'.
+
 5 How to Ask for Help
 *********************
 
@@ -1520,6 +1540,8 @@ can not be sure.
 Appendix A Revision History of This Document
 ********************************************
 
+   * Rev 2.16 (JD) Added 4.33.2, 2005-09-06
+
    * Rev 2.15 (JD) Updates, including mailing-list change, 2005-05-21
 
    * Rev 2.14 (MDS) Updated 4.12, 2004-11-26

doc/lm_sensors-FAQ.html

@@ -1,8 +1,8 @@
 <html lang="en">
 <head>
-<title>Sensors FAQ for lm_sensors version 2.15</title>
+<title>Sensors FAQ for lm_sensors version 2.16</title>
 <meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Sensors FAQ for lm_sensors version 2.15">
+<meta name="description" content="Sensors FAQ for lm_sensors version 2.16">
 <meta name="generator" content="makeinfo 4.7">
 <link title="Top" rel="top" href="#Top">
 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
@@ -19,7 +19,7 @@
 --></style>
 </head>
 <body>
-<h1 class="settitle">Sensors FAQ for lm_sensors version 2.15</h1>
+<h1 class="settitle">Sensors FAQ for lm_sensors version 2.16</h1>
 Copyright (C) 1998 - 2005<br>
 Frodo Looijaard,<br>
 Philip Edelbrock,<br>
@@ -168,6 +168,7 @@ Jean Delvare<br>
 <li><a href="#Section-4_002e33">4.33 Problems on 2.6 kernels</a>
 <ul>
 <li><a href="#Section-4_002e33">4.33.1 i2c-viapro and via686a</a>
+<li><a href="#Section-4_002e33">4.33.2 Where are my EEPROMs?</a>
 </li></ul>
 </li></ul>
 <li><a name="toc_Help" href="#Help">5 How to Ask for Help</a>
@@ -1758,6 +1759,26 @@ sensors driver for VIA bridges). This caused the second loaded driver to
 silently fail working. So do not load both i2c-viapro and via686a together
 unless you have a recent kernel.
 
+<h4 class="subsection">4.33.2 Where are my EEPROMs?</h4>
+
+<p>The 2.6.14-rc1 kernel introduced the hwmon class, which groups all
+hardware monitoring drivers in a logical way. The goal was to help
+libsensors grab the relevant sensors information in /sys. In particular:
+     <ul>
+<li>libsensors will no more need to know about the underlying bus types
+(I2C/SMBus, ISA or other);
+<li>libsensors will no more list non-hardware monitoring chips. 
+</ul>
+   This explains why EEPROMs are no more displayed by <span class="command">sensors</span>:
+they are no hardware monitoring chips. The medium term plan is to drop
+eeprom support for all Linux 2.6 kernels, as it didn't fit well in
+the library code in the first place.
+
+   <p>Note that you can still obtain information about your EEPROMs by using
+the dedicated perl scripts in <span class="file">prog/eeprom</span>: <span class="command">ddcmon</span>,
+<span class="command">decode-dimms.pl</span>, <span class="command">decode-edid.pl</span> and
+<span class="command">decode-vaio.pl</span>.
+
 <div class="node">
 <p><hr>
 <a name="Help"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Contribute">Contribute</a>,
@@ -2222,6 +2243,7 @@ Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
 <h2 class="appendix">Appendix A Revision History of This Document</h2>
 
      <ul>
+<li>Rev 2.16 (JD) Added 4.33.2, 2005-09-06
 <li>Rev 2.15 (JD) Updates, including mailing-list change, 2005-05-21
 <li>Rev 2.14 (MDS) Updated 4.12, 2004-11-26
 <li>Rev 2.13 (JD) Added 4.6.1, updated 4.7, 2004-06-23

doc/lm_sensors-FAQ.texi

@@ -1258,8 +1258,8 @@ For IBM systems, see @file{README.thinkpad}.
 @section Problems on 2.6 kernels
 
 Not all drivers have been ported to 2.6. If your favorite driver is not
-in 2.6, the reason is that nobody has ported it.
-Please don't bother asking us why it is not in 2.6.
+in 2.6, the reason is that nobody has ported it, or the ported code did
+not get a proper review yet.
 If you would like to port the driver, see the file
 Documentation/i2c/porting-clients in the 2.6 kernel tree for help,
 then send us the ported driver when you are done.
@@ -1271,6 +1271,25 @@ sensors driver for VIA bridges). This caused the second loaded driver to
 silently fail working. So do not load both i2c-viapro and via686a together 
 unless you have a recent kernel.
 
+@subsection Where are my EEPROMs?
+The 2.6.14-rc1 kernel introduced the hwmon class, which groups all
+hardware monitoring drivers in a logical way. The goal was to help
+libsensors grab the relevant sensors information in /sys. In particular:
+@itemize
+@item libsensors will no more need to know about the underlying bus types
+(I2C/SMBus, ISA or other);
+@item libsensors will no more list non-hardware monitoring chips.
+@end itemize
+This explains why EEPROMs are no more displayed by @command{sensors}:
+they are no hardware monitoring chips. The medium term plan is to drop
+eeprom support for all Linux 2.6 kernels, as it didn't fit well in
+the library code in the first place.
+
+Note that you can still obtain information about your EEPROMs by using
+the dedicated perl scripts in @file{prog/eeprom}: @command{ddcmon},
+@command{decode-dimms.pl}, @command{decode-edid.pl} and
+@command{decode-vaio.pl}.
+
 
 @node Help, Contribute, Problems, Top
 @chapter How to Ask for Help
@@ -1591,6 +1610,7 @@ can not be sure.
 @appendix Revision History of This Document
 
 @itemize
+@item Rev 2.16 (JD) Added 4.33.2, 2005-09-06
 @item Rev 2.15 (JD) Updates, including mailing-list change, 2005-05-21
 @item Rev 2.14 (MDS) Updated 4.12, 2004-11-26
 @item Rev 2.13 (JD) Added 4.6.1, updated 4.7, 2004-06-23

doc/version.texi

@@ -1,2 +1,2 @@
-@set UPDATED 21 May 2004
-@set VERSION 2.15
+@set UPDATED 6 September 2004
+@set VERSION 2.16