patch-pre2.0.6 linux/Documentation/cdrom/ide-cd

• Lines: 97
• Date: Sun May 19 15:16:34 1996
• Orig file: pre2.0.5/linux/Documentation/cdrom/ide-cd
• Orig date: Sun May 12 22:54:22 1996

diff -u --recursive --new-file pre2.0.5/linux/Documentation/cdrom/ide-cd linux/Documentation/cdrom/ide-cd
@@ -1,5 +1,5 @@
 IDE-CD driver documentation
-10 May 1996
+19 May 1996
 scott snyder  <snyder@fnald0.fnal.gov>
 
 1. Introduction
@@ -45,7 +45,7 @@
 ---------------
 
 0. The ide-cd relies on the ide disk driver.  See
-   drivers/block/README.ide for up-to-date information on the ide
+   Documentation/ide.txt for up-to-date information on the ide
    driver.
 
 1. Make sure that the ide and ide-cd drivers are compiled into the
@@ -61,7 +61,7 @@
 
    Depending on what type of IDE interface you have, you may need to
    specify additional configuration options.  See
-   drivers/block/README.ide.
+   Documentation/ide.txt.
 
 2. You should also ensure that the iso9660 filesystem is either
    compiled into the kernel or available as a loadable module.  You
@@ -81,7 +81,7 @@
    on the primary IDE interface are called `hda' and `hdb',
    respectively.  The drives on the secondary interface are called
    `hdc' and `hdd'.  (Interfaces at other locations get other letters
-   in the third position; see drivers/block/README.ide.)
+   in the third position; see Documentation/ide.txt.)
 
    If you want your cdrom drive to be found automatically by the
    driver, you should make sure your IDE interface uses either the
@@ -90,7 +90,7 @@
    be jumpered as `master'.  (If for some reason you cannot configure
    your system in this manner, you can probably still use the driver.
    You may have to pass extra configuration information to the kernel
-   when you boot, however.  See drivers/block/README.ide for more
+   when you boot, however.  See Documentation/ide.txt for more
    information.)
 
 4. Boot the system.  If the drive is recognized, you should see a
@@ -194,7 +194,7 @@
 This section discusses some common problems encountered when trying to
 use the driver, and some possible solutions.  Note that if you are
 experiencing problems, you should probably also review
-drivers/block/README.ide for current information about the underlying
+Documentation/ide.txt for current information about the underlying
 IDE support code.  Some of these items apply only to earlier versions
 of the driver, but are mentioned here for completeness.
 
@@ -204,7 +204,7 @@
 a. Drive is not detected during booting.
 
    - Review the configuration instructions above and in
-     drivers/block/README.ide, and check how your hardware is
+     Documentation/ide.txt, and check how your hardware is
      configured.
 
    - If your drive is the only device on an IDE interface, it should
@@ -212,7 +212,7 @@
 
    - If your IDE interface is not at the standard addresses of 0x170
      or 0x1f0, you'll need to explicitly inform the driver using a
-     lilo option.  See drivers/block/README.ide.  (This feature was
+     lilo option.  See Documentation/ide.txt.  (This feature was
      added around kernel version 1.3.30.)
 
    - If the autoprobing is not finding your drive, you can tell the
@@ -238,7 +238,7 @@
      Support for some interfaces needing extra initialization is
      provided in later 1.3.x kernels.  You may need to turn on
      additional kernel configuration options to get them to work;
-     see drivers/block/README.ide.
+     see Documentation/ide.txt.
 
      Even if support is not available for your interface, you may be
      able to get it to work with the following procedure.  First boot
@@ -283,7 +283,7 @@
     be worked around by specifying the `serialize' option when
     booting.  Recent kernels should be able to detect the need for
     this automatically in most cases, but the detection is not
-    foolproof.  See drivers/block/README.ide for more information
+    foolproof.  See Documentation/ide.txt for more information
     about the `serialize' option and the CMD640B.
 
   - Note that many MS-DOS cdrom drivers will work with such buggy
@@ -319,7 +319,7 @@
 
     Some early Slackware releases had these defined incorrectly.  If
     these are wrong, you can remake them by running the script
-    drivers/block/MAKEDEV.ide.  (You may have to make it executable
+    scripts/MAKEDEV.ide.  (You may have to make it executable
     with chmod first.)
 
     If you have a /dev/cdrom symbolic link, check that it is pointing