Commit 25eb650a authored by Wanlong Gao's avatar Wanlong Gao Committed by Jiri Kosina
Browse files

doc: fix wrong arch/i386 references 



Change all "arch/i386" to "arch/x86" in Documentaion/,
since the directory has changed.

Also update the files which have changed their filename
in the meantime accordingly.

Signed-off-by: default avatarWanlong Gao <wanlong.gao@gmail.com>
[jkosina@suse.cz: reword changelog]
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent c443453c

Documentation/RCU/NMI-RCU.txt

+2 −2
Original line number Original line Diff line number Diff line
@@ -5,8 +5,8 @@ Although RCU is usually used to protect read-mostly data structures, 
it is possible to use RCU to provide dynamic non-maskable interrupt

it is possible to use RCU to provide dynamic non-maskable interrupt

handlers, as well as dynamic irq handlers.  This document describes

handlers, as well as dynamic irq handlers.  This document describes

how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer

how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer

work in "arch/i386/oprofile/nmi_timer_int.c" and in

work in "arch/x86/oprofile/nmi_timer_int.c" and in

"arch/i386/kernel/traps.c".

"arch/x86/kernel/traps.c".





The relevant pieces of code are listed below, each followed by a

The relevant pieces of code are listed below, each followed by a

brief explanation.

brief explanation.

Documentation/blockdev/README.DAC960

+1 −1
Original line number Original line Diff line number Diff line
@@ -214,7 +214,7 @@ replacing "/usr/src" with wherever you keep your Linux kernel source tree: 
  make config

  make config

  make bzImage (or zImage)

  make bzImage (or zImage)





Then install "arch/i386/boot/bzImage" or "arch/i386/boot/zImage" as your

Then install "arch/x86/boot/bzImage" or "arch/x86/boot/zImage" as your

standard kernel, run lilo if appropriate, and reboot.

standard kernel, run lilo if appropriate, and reboot.





To create the necessary devices in /dev, the "make_rd" script included in

To create the necessary devices in /dev, the "make_rd" script included in

Documentation/blockdev/ramdisk.txt

+4 −4
Original line number Original line Diff line number Diff line
@@ -64,9 +64,9 @@ the RAM disk dynamically grows as data is being written into it, a size field 
is not required. Bits 11 to 13 are not currently used and may as well be zero.

is not required. Bits 11 to 13 are not currently used and may as well be zero.

These numbers are no magical secrets, as seen below:

These numbers are no magical secrets, as seen below:





./arch/i386/kernel/setup.c:#define RAMDISK_IMAGE_START_MASK     0x07FF

./arch/x86/kernel/setup.c:#define RAMDISK_IMAGE_START_MASK     0x07FF

./arch/i386/kernel/setup.c:#define RAMDISK_PROMPT_FLAG          0x8000

./arch/x86/kernel/setup.c:#define RAMDISK_PROMPT_FLAG          0x8000

./arch/i386/kernel/setup.c:#define RAMDISK_LOAD_FLAG            0x4000

./arch/x86/kernel/setup.c:#define RAMDISK_LOAD_FLAG            0x4000





Consider a typical two floppy disk setup, where you will have the

Consider a typical two floppy disk setup, where you will have the

kernel on disk one, and have already put a RAM disk image onto disk #2.

kernel on disk one, and have already put a RAM disk image onto disk #2.
@@ -85,7 +85,7 @@ The command line equivalent is: "prompt_ramdisk=1" 
Putting that together gives 2^15 + 2^14 + 0 = 49152 for an rdev word.

Putting that together gives 2^15 + 2^14 + 0 = 49152 for an rdev word.

So to create disk one of the set, you would do:

So to create disk one of the set, you would do:





	/usr/src/linux# cat arch/i386/boot/zImage > /dev/fd0

	/usr/src/linux# cat arch/x86/boot/zImage > /dev/fd0

	/usr/src/linux# rdev /dev/fd0 /dev/fd0

	/usr/src/linux# rdev /dev/fd0 /dev/fd0

	/usr/src/linux# rdev -r /dev/fd0 49152

	/usr/src/linux# rdev -r /dev/fd0 49152

Documentation/cpu-freq/cpu-drivers.txt

+1 −1
Original line number Original line Diff line number Diff line
@@ -168,7 +168,7 @@ in-chipset dynamic frequency switching to policy->min, the upper limit 
to policy->max, and -if supported- select a performance-oriented

to policy->max, and -if supported- select a performance-oriented

setting when policy->policy is CPUFREQ_POLICY_PERFORMANCE, and a

setting when policy->policy is CPUFREQ_POLICY_PERFORMANCE, and a

powersaving-oriented setting when CPUFREQ_POLICY_POWERSAVE. Also check

powersaving-oriented setting when CPUFREQ_POLICY_POWERSAVE. Also check

the reference implementation in arch/i386/kernel/cpu/cpufreq/longrun.c

the reference implementation in drivers/cpufreq/longrun.c

Documentation/filesystems/nfs/nfsroot.txt

+1 −1
Original line number Original line Diff line number Diff line
@@ -226,7 +226,7 @@ They depend on various facilities being available: 
     	cdrecord.

     	cdrecord.





	e.g.

	e.g.

	  cdrecord dev=ATAPI:1,0,0 arch/i386/boot/image.iso

	  cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso





     	For more information on isolinux, including how to create bootdisks

     	For more information on isolinux, including how to create bootdisks

     	for prebuilt kernels, see http://syslinux.zytor.com/

     	for prebuilt kernels, see http://syslinux.zytor.com/