From 4d5a7df8866dc2e98b645bf20521e60409246186 Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Sat, 17 Dec 2005 11:25:33 +0000 Subject: [PATCH] Remove the version 1 specifics part. It's very old and I'd hope nobody uses this anymore. At any rate, there's little point in including version 1 information in the version 2 FAQ. Set FAQ version to 2.18. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3216 7894878c-1315-0410-8ee3-d5d059ff63e0 --- doc/FAQ | 65 +--------------------- doc/lm_sensors-FAQ.html | 118 +++------------------------------------- doc/lm_sensors-FAQ.texi | 75 +------------------------ doc/version.texi | 4 +- 4 files changed, 14 insertions(+), 248 deletions(-) diff --git a/doc/FAQ b/doc/FAQ index 045ae531..bd3f9532 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -8,7 +8,6 @@ lm_sensors 4 Problems 5 How to Ask for Help 6 How to Contribute -7 Version 1 Specific Questions Appendix A Revision History of This Document @@ -128,11 +127,6 @@ lm_sensors 6.6 How to submit a patch 6.7 How to REALLY help 6.8 How to get release announcements -7 Version 1 Specific Questions - 7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong? - 7.2 The modules won't load, saying 'SMBus not detected'. - 7.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why? - 7.4 On my Dell, a LM80 is detected, but all readings are 0! Appendix A Revision History of This Document @@ -1539,66 +1533,11 @@ register on our freshmeat project page `http://freshmeat.net/projects/lm_sensors' to 'subscribe to new releases' and then freshmeat will email you announcement. -7 Version 1 Specific Questions -****************************** - -Note: Version 1 is very very old and is not recommended. - -7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong? -====================================================================================================================== - -Currently, our code only assumes that an SMBus exists if it originates -from the Intel PIIX4 (82371AB). If your computer doesn't have one, or -if your SMBus originates from a different SMBus 'host', then you are -out of luck. :'( Our experience is, though, that most machines have a -PIIX4, and that it is where the SMBus is hosted. - - Regarding the VIA chip set(s): - - Right now, the SMBus code depends on the Intel PIIX4 chip to handle -SMBus transactions. The VIA chip set is NOT supported at this time -because it forces much of the SMBus protocol to be implemented by -software. - - To implement the SMBus correctly with the VIA chip, it needs to be -written at a low level to be quick. A more attractive alternative is to -use the Bios SMBus interface (not always available nor standard). - - Version 2 supports the VIA chipset, and will support other chipsets. -Version 1 never will. - -7.2 The modules won't load, saying 'SMBus not detected'. -======================================================== - -This should no longer be an issue in 1.4.10 and later; it will continue -loading, but it won't support SMBus-connected devices, of course. - -7.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why? -============================================================================================================== - -It takes about 1.5 seconds for the LM78 to update all its sensor -values. If we would try to read it before it finished that, you would -get old garbage instead. So you have to wait 1.5 seconds after the -module is inserted before you can access `/proc/sensors'. - - Module versions 1.3.7 and later let the process sleep if it tries to -access sensor data right after insertion time, and do not display this -message anymore. - -7.4 On my Dell, a LM80 is detected, but all readings are 0! -=========================================================== - -This is a bug we have only observed on Dell computers. There is -probably a problem with the way the SMBus is accessed; but it is not yet -clear whether the problem is in our code or with the Dells. - - There are very probably no sensor chips at all on your computer; but -until somebody contacts Dell about this and tells us the results, we -can not be sure. - Appendix A Revision History of This Document ******************************************** + * Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17 + * Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips), removed 6.9 (doesn't apply to the new mailing list), 2005-10-05 diff --git a/doc/lm_sensors-FAQ.html b/doc/lm_sensors-FAQ.html index db564a03..69f833a8 100644 --- a/doc/lm_sensors-FAQ.html +++ b/doc/lm_sensors-FAQ.html @@ -1,8 +1,8 @@ -Sensors FAQ for lm_sensors version 2.17 +Sensors FAQ for lm_sensors version 2.18 - + @@ -19,7 +19,7 @@ --> -

Sensors FAQ for lm_sensors version 2.17

+

Sensors FAQ for lm_sensors version 2.18

Copyright (C) 1998 - 2005
Frodo Looijaard,
Philip Edelbrock,
@@ -37,7 +37,6 @@ Jean Delvare
  • 4 Problems
  • 5 How to Ask for Help
  • 6 How to Contribute
    • -
  • 7 Version 1 Specific Questions
  • Appendix A Revision History of This Document
    • @@ -194,13 +193,6 @@ Jean Delvare
  • 6.7 How to REALLY help
  • 6.8 How to get release announcements
    • -
  • 7 Version 1 Specific Questions -
  • Appendix A Revision History of This Document
    • @@ -225,8 +217,7 @@ is not in standard 2.2-vintage kernels.
  • Problems: Problems
  • Help: How to Ask for Help
  • Contribute: How to Contribute -
  • Version 1 Specifics: Version 1 Specific Questions -
  • Document Revisions: Revision History of This Document +
  • Document Revisions: Revision History of This Document
    @@ -2034,7 +2025,7 @@ driver, we will apply it. This generic code is unlikely to cause trouble.

    -Next: , +Next: , Previous: Help, Up: Top
    @@ -2195,103 +2186,7 @@ will email you announcement.

    -Next: , -Previous: Contribute, -Up: Top -
    -
    - -

    7 Version 1 Specific Questions

    - -
      -
    • Section 7.1: My mainboard has an SMBus, your code can't find it. Why? -
    • Section 7.2: The modules won't load, saying 'SMBus not detected'. -
    • Section 7.3: I get a "No sensor data yet (try again in a few moments)" msg. -
    • Section 7.4: On my Dell, a LM80 is detected, but all readings are 0! -
    - -

    Note: Version 1 is very very old and is not recommended. - -

    -

    -Next: , -Up: Version 1 Specifics -
    -
    - -

    7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?

    - -

    Currently, our code only assumes that an SMBus exists if it originates -from the Intel PIIX4 (82371AB). If your computer doesn't have one, or if your -SMBus originates from a different SMBus 'host', then you are out of luck. :'( -Our experience is, though, that most machines have a PIIX4, and that it is -where the SMBus is hosted. - -

    Regarding the VIA chip set(s): - -

    Right now, the SMBus code depends on the Intel PIIX4 chip to handle -SMBus transactions. The VIA chip set is NOT supported at this time because -it forces much of the SMBus protocol to be implemented by software. - -

    To implement the SMBus correctly with the VIA chip, it needs to be -written at a low level to be quick. A more attractive alternative is to -use the Bios SMBus interface (not always available nor standard). - -

    Version 2 supports the VIA chipset, and will support other chipsets. -Version 1 never will. - -

    -

    -Next: , -Previous: Section 7.1, -Up: Version 1 Specifics -
    -
    - -

    7.2 The modules won't load, saying 'SMBus not detected'.

    - -

    This should no longer be an issue in 1.4.10 and later; it will -continue loading, but it won't support SMBus-connected devices, of course. - -

    -

    -Next: , -Previous: Section 7.2, -Up: Version 1 Specifics -
    -
    - -

    7.3 I try to read /proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?

    - -

    It takes about 1.5 seconds for the LM78 to update all its sensor -values. If we would try to read it before it finished that, you would get -old garbage instead. So you have to wait 1.5 seconds after the module is -inserted before you can access /proc/sensors. - -

    Module versions 1.3.7 and later let the process sleep if it tries -to access sensor data right after insertion time, and do not display this -message anymore. - -

    -

    -Previous: Section 7.3, -Up: Version 1 Specifics -
    -
    - -

    7.4 On my Dell, a LM80 is detected, but all readings are 0!

    - -

    This is a bug we have only observed on Dell computers. There is -probably a problem with the way the SMBus is accessed; but it is not yet -clear whether the problem is in our code or with the Dells. - -

    There are very probably no sensor chips at all on your computer; -but until somebody contacts Dell about this and tells us the results, we -can not be sure. - -

    -

    -Previous: Version 1 Specifics, +Previous: Contribute, Up: Top
    @@ -2299,6 +2194,7 @@ Up: Top

    Appendix A Revision History of This Document

      +
    • Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
    • Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips), removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
    • Rev 2.16 (JD) Added 4.33.2, 2005-09-06 diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index 10b5d6f4..5e9c6965 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -52,7 +52,6 @@ is not in standard 2.2-vintage kernels. * Problems:: Problems * Help:: How to Ask for Help * Contribute:: How to Contribute -* Version 1 Specifics:: Version 1 Specific Questions * Document Revisions:: Revision History of This Document @end menu @@ -1486,7 +1485,7 @@ provides a patch to libsensors and/or sensors to add support for this driver, we will apply it. This generic code is unlikely to cause trouble. -@node Contribute, Version 1 Specifics, Help, Top +@node Contribute, Document Revisions, Help, Top @chapter How to Contribute @menu @@ -1594,79 +1593,11 @@ to 'subscribe to new releases' and then freshmeat will email you announcement. -@node Version 1 Specifics, Document Revisions, Contribute, Top -@chapter Version 1 Specific Questions - -@menu -* Section 7.1:: My mainboard has an SMBus, your code can't find it. Why? -* Section 7.2:: The modules won't load, saying 'SMBus not detected'. -* Section 7.3:: I get a "No sensor data yet (try again in a few moments)" msg. -* Section 7.4:: On my Dell, a LM80 is detected, but all readings are 0! -@end menu - - -Note: Version 1 is very very old and is not recommended. - -@node Section 7.1, Section 7.2, , Version 1 Specifics -@section My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong? - -Currently, our code only assumes that an SMBus exists if it originates -from the Intel PIIX4 (82371AB). If your computer doesn't have one, or if your -SMBus originates from a different SMBus 'host', then you are out of luck. :'( -Our experience is, though, that most machines have a PIIX4, and that it is -where the SMBus is hosted. - -Regarding the VIA chip set(s): - -Right now, the SMBus code depends on the Intel PIIX4 chip to handle -SMBus transactions. The VIA chip set is NOT supported at this time because -it forces much of the SMBus protocol to be implemented by software. - -To implement the SMBus correctly with the VIA chip, it needs to be -written at a low level to be quick. A more attractive alternative is to -use the Bios SMBus interface (not always available nor standard). - - -Version 2 supports the VIA chipset, and will support other chipsets. -Version 1 never will. - - -@node Section 7.2, Section 7.3, Section 7.1, Version 1 Specifics -@section The modules won't load, saying 'SMBus not detected'. - -This should no longer be an issue in 1.4.10 and later; it will -continue loading, but it won't support SMBus-connected devices, of course. - - -@node Section 7.3, Section 7.4, Section 7.2, Version 1 Specifics -@section I try to read @file{/proc/sensors}, and I get a "No sensor data yet (try again in a few moments)" message. Why? - -It takes about 1.5 seconds for the LM78 to update all its sensor -values. If we would try to read it before it finished that, you would get -old garbage instead. So you have to wait 1.5 seconds after the module is -inserted before you can access @file{/proc/sensors}. - -Module versions 1.3.7 and later let the process sleep if it tries -to access sensor data right after insertion time, and do not display this -message anymore. - - -@node Section 7.4, , Section 7.3, Version 1 Specifics -@section On my Dell, a LM80 is detected, but all readings are 0! - -This is a bug we have only observed on Dell computers. There is -probably a problem with the way the SMBus is accessed; but it is not yet -clear whether the problem is in our code or with the Dells. - -There are very probably no sensor chips at all on your computer; -but until somebody contacts Dell about this and tells us the results, we -can not be sure. - - -@node Document Revisions, , Version 1 Specifics, Top +@node Document Revisions, , Contribute, Top @appendix Revision History of This Document @itemize +@item Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17 @item Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips), removed 6.9 (doesn't apply to the new mailing list), 2005-10-05 @item Rev 2.16 (JD) Added 4.33.2, 2005-09-06 diff --git a/doc/version.texi b/doc/version.texi index 328878c2..f9ae6f78 100644 --- a/doc/version.texi +++ b/doc/version.texi @@ -1,2 +1,2 @@ -@set UPDATED 5 October 2005 -@set VERSION 2.17 +@set UPDATED 17 December 2005 +@set VERSION 2.18