From cf37dc2040cea9f384bd7d3dcaf24014f441b8a6 Mon Sep 17 00:00:00 2001 From: Sascha Wildner Date: Sun, 20 Sep 2015 01:40:47 +0200 Subject: [PATCH] i386 removal, part 43/x: Remove/change i386 specific info in manual pages. --- sbin/disklabel32/disklabel32.8 | 24 ------------------------ sbin/disklabel64/disklabel64.8 | 24 ------------------------ sbin/reboot/boot_pc64.8 | 9 +++++---- share/examples/mdoc/example.4 | 2 +- share/man/man3/fpgetround.3 | 2 +- share/man/man4/acpi.4 | 7 +------ share/man/man4/arcmsr.4 | 2 +- share/man/man4/cpuctl.4 | 3 +-- share/man/man4/ddb.4 | 5 +++-- share/man/man4/ppbus.4 | 3 +-- share/man/man5/kernconf.5 | 16 ++-------------- share/man/man5/procfs.5 | 3 --- share/man/man7/tuning.7 | 4 +--- share/man/man9/atomic.9 | 17 ----------------- share/man/man9/bus_dma.9 | 2 +- share/man/man9/lwbuf.9 | 11 ++--------- usr.bin/locate/locate/locate.1 | 3 +-- usr.sbin/boot0cfg/boot0cfg.8 | 2 +- usr.sbin/config/config.8 | 4 ++-- 19 files changed, 24 insertions(+), 119 deletions(-) diff --git a/sbin/disklabel32/disklabel32.8 b/sbin/disklabel32/disklabel32.8 index 085bbe4a1d..f3d985b933 100644 --- a/sbin/disklabel32/disklabel32.8 +++ b/sbin/disklabel32/disklabel32.8 @@ -1005,30 +1005,6 @@ for read-only operation. .Xr newfs_hammer 8 , .Xr vinum 8 .Sh BUGS -For the i386 architecture, the primary bootstrap sector contains -an embedded -.Em fdisk -table. -The -.Nm -utility takes care to not clobber it when installing a bootstrap only -.Pq Fl B , -or when editing an existing label -.Pq Fl e , -but it unconditionally writes the primary bootstrap program onto -the disk for -.Fl w -or -.Fl R , -thus replacing the -.Em fdisk -table by the dummy one in the bootstrap program. -This is only of -concern if the disk is fully dedicated, so that the -.Bx -disklabel -starts at absolute block 0 on the disk. -.Pp The .Nm utility diff --git a/sbin/disklabel64/disklabel64.8 b/sbin/disklabel64/disklabel64.8 index e5526acaf0..61d44cfa80 100644 --- a/sbin/disklabel64/disklabel64.8 +++ b/sbin/disklabel64/disklabel64.8 @@ -935,30 +935,6 @@ partition. .Xr newfs_hammer 8 , .Xr vinum 8 .Sh BUGS -For the i386 architecture, the primary bootstrap sector contains -an embedded -.Em fdisk -table. -The -.Nm -utility takes care to not clobber it when installing a bootstrap only -.Pq Fl B , -or when editing an existing label -.Pq Fl e , -but it unconditionally writes the primary bootstrap program onto -the disk for -.Fl w -or -.Fl R , -thus replacing the -.Em fdisk -table by the dummy one in the bootstrap program. -This is only of -concern if the disk is fully dedicated, so that the -.Bx -disklabel -starts at absolute block 0 on the disk. -.Pp The .Nm utility diff --git a/sbin/reboot/boot_pc64.8 b/sbin/reboot/boot_pc64.8 index 7522539d0a..b1d301beb8 100644 --- a/sbin/reboot/boot_pc64.8 +++ b/sbin/reboot/boot_pc64.8 @@ -49,10 +49,11 @@ An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. .Pp .Sy Cold starts . -Most i386 PCs attempt to boot first from floppy disk drive 0 (sometimes -known as drive A:) and, failing that, from hard disk drive 0 (sometimes -known as drive C:, or as drive 0x80 to the BIOS). Some BIOSes allow -you to change this default sequence, and may also include a CD-ROM +Most PCs attempt to boot first from hard disk drive 0 (sometimes +known as drive C:) and, failing that, from various other mass storage +devices. +Usually, BIOSes allow +you to change this default sequence, and typically also include a CD-ROM drive as a boot device. .Pp By default, a three-stage bootstrap is employed, and control is diff --git a/share/examples/mdoc/example.4 b/share/examples/mdoc/example.4 index 4c9b39ec96..69bd069090 100644 --- a/share/examples/mdoc/example.4 +++ b/share/examples/mdoc/example.4 @@ -27,7 +27,7 @@ .\" Note: The date here should be updated whenever a non-trivial .\" change is made to the manual page. .Dd December 8, 1999 -.Dt EXAMPLE 4 i386 +.Dt EXAMPLE 4 .Os .Sh NAME .Nm example diff --git a/share/man/man3/fpgetround.3 b/share/man/man3/fpgetround.3 index 28793441be..106089033c 100644 --- a/share/man/man3/fpgetround.3 +++ b/share/man/man3/fpgetround.3 @@ -160,7 +160,7 @@ The and .Fn fpsetprec functions provide functionality unavailable on many platforms. -At present, they are implemented only on the i386 and x86_64 platforms. +At present, they are implemented only on the x86_64 platform. Changing precision is not a supported feature: it may be ineffective when code is compiled to take advantage of SSE, and many library functions and compiler optimizations depend upon the diff --git a/share/man/man4/acpi.4 b/share/man/man4/acpi.4 index 8073cf52ca..f48bd2dd17 100644 --- a/share/man/man4/acpi.4 +++ b/share/man/man4/acpi.4 @@ -325,10 +325,7 @@ driver completely, set the kernel environment variable .Va hint.acpi.0.disabled to 1. .Pp -Some i386 machines totally fail to operate with some or all of ACPI disabled. -Other i386 machines fail with ACPI enabled. -Disabling all or part of ACPI on non-i386 platforms (i.e., platforms where -ACPI support is mandatory) may result in a non-functional system. +Disabling all or part of ACPI may result in a non-functional system. .Pp The .Nm @@ -621,8 +618,6 @@ In order to prepare your AML code, you will need the and .Xr iasl 8 utilities and some ACPI knowledge. -.\".Sh COMPATIBILITY -.\"ACPI is only found and supported on i386 and x86_64. .Sh SEE ALSO .Xr kenv 1 , .Xr acpi_asus 4 , diff --git a/share/man/man4/arcmsr.4 b/share/man/man4/arcmsr.4 index 8037326cba..44309448dd 100644 --- a/share/man/man4/arcmsr.4 +++ b/share/man/man4/arcmsr.4 @@ -64,7 +64,7 @@ device nodes. A management interface is also present via the .Pa /dev/arcmsr? device node. -Management tools for i386 and amd64 are available from Areca. +.\"Management tools for i386 and amd64 are available from Areca. .Sh LOADER TUNABLES .Bl -tag -width indent .It Va hw.arcmsr.msi.enable diff --git a/share/man/man4/cpuctl.4 b/share/man/man4/cpuctl.4 index 351f7ef002..4d920158ab 100644 --- a/share/man/man4/cpuctl.4 +++ b/share/man/man4/cpuctl.4 @@ -58,8 +58,7 @@ with the appropriate index will be created. For multicore CPUs such a special device will be created for each core. .Pp -Currently, only i386 and x86_64 processors are -supported. +Currently, only x86_64 processors are supported. .Sh IOCTL INTERFACE All of the supported operations are invoked using the .Xr ioctl 2 diff --git a/share/man/man4/ddb.4 b/share/man/man4/ddb.4 index 72f435944b..c393018337 100644 --- a/share/man/man4/ddb.4 +++ b/share/man/man4/ddb.4 @@ -198,7 +198,8 @@ The location is also displayed in hex at the beginning of each line. .It Li i display as an instruction .It Li I -display as an instruction; on i386, don't round to the next long word boundary. +alias for +.Li i .El .It Cm xf Examine forward: @@ -448,7 +449,7 @@ with an error message. .Pp .Sy Warning : Attempts to watch wired kernel memory -may cause unrecoverable error in some systems such as i386. +may cause unrecoverable error in some systems. Watchpoints on user addresses work best. .It Cm acpidb If the kernel was compiled with diff --git a/share/man/man4/ppbus.4 b/share/man/man4/ppbus.4 index 004573fb09..780e5bd7d9 100644 --- a/share/man/man4/ppbus.4 +++ b/share/man/man4/ppbus.4 @@ -97,8 +97,7 @@ functions to initialize the ppbus system. .Sh PARALLEL PORT MODEL The logical parallel port model chosen for the ppbus system is the PC's parallel port model. -Consequently, for the i386 implementation of ppbus, -most of the services provided by ppc are macros for +Consequently, most of the services provided by ppc are macros for .Fn inb and .Fn outb diff --git a/share/man/man5/kernconf.5 b/share/man/man5/kernconf.5 index 2751dd9095..090f29748c 100644 --- a/share/man/man5/kernconf.5 +++ b/share/man/man5/kernconf.5 @@ -75,17 +75,7 @@ The following keywords are recognized in a configuration file: .It Sy cpu Ar name This system is to run on the CPU type .Ar name . -Legal types are, for -.Sy i386 : -.Sy I486_CPU -(i486), -.Sy I586_CPU -.Tn ( Pentium ) , -and -.Sy I686_CPU -.Tn ( Pentium Pro ) ; -for -.Sy x86_64 : +Legal types are: .Sy HAMMER_CPU .Tn ( x86-64 ) . More than one CPU type specification can appear in a configuration file. @@ -137,9 +127,7 @@ This is a legacy keyword, it is normally set to same value as .It Sy machine_arch Ar name The system is to run on the machine architecture .Ar name . -The legal architectures are -.Sy i386 , -and +Currently, the only legal architecture is .Sy x86_64 . .Pp .It Sy makeoptions Ar name Ns Sy = Ns Ar value diff --git a/share/man/man5/procfs.5 b/share/man/man5/procfs.5 index 443df3155d..bf0246570e 100644 --- a/share/man/man5/procfs.5 +++ b/share/man/man5/procfs.5 @@ -1,5 +1,4 @@ .\" $FreeBSD: src/share/man/man5/procfs.5,v 1.14.2.5 2001/08/17 13:08:47 ru Exp $ -.\" $DragonFly: src/share/man/man5/procfs.5,v 1.3 2006/05/26 19:39:40 swildner Exp $ .\" Written by Garrett Wollman .\" This file is in the public domain. .\" @@ -80,8 +79,6 @@ The debug registers as defined by .Dv "struct dbregs" in .In machine/reg.h . -.Pa dbregs -is currently only implemented on the i386 architecture. .It Pa etype The type of the executable referenced by the .Pa file diff --git a/share/man/man7/tuning.7 b/share/man/man7/tuning.7 index c3b892edeb..fef875b4f6 100644 --- a/share/man/man7/tuning.7 +++ b/share/man/man7/tuning.7 @@ -2,8 +2,6 @@ .\" the BSD Copyright as specified in the file "/usr/src/COPYRIGHT" in .\" the source tree. .\" -.\" $DragonFly: src/share/man/man7/tuning.7,v 1.21 2008/10/17 11:30:24 swildner Exp $ -.\" .Dd October 24, 2010 .Dt TUNING 7 .Os @@ -50,7 +48,7 @@ maximizing the ram available for your activities. If you intend to use the .Xr swapcache 8 facility with a SSD we recommend the SSD be configured with at -least a 32G swap partition (the maximum default for i386). +least a 32G swap partition. If you are on a moderately well configured 64-bit system you can size swap even larger. .Pp diff --git a/share/man/man9/atomic.9 b/share/man/man9/atomic.9 index 006d7b798b..70b135852f 100644 --- a/share/man/man9/atomic.9 +++ b/share/man/man9/atomic.9 @@ -163,14 +163,6 @@ operation need to be atomic on the processor performing the operation, but the result of the operation needs to be pushed out to stable storage and the caches of all other processors on the system need to invalidate any cache lines that include the affected memory region. -On the -.Tn i386 -architecture, the cache coherency model requires that the hardware perform -this task, thus the atomic operations are atomic across multiple processors. -.\"On the -.\".Tn ia64 -.\"architecture, coherency is only guaranteed for pages that are configured to -.\"using a caching policy of either uncached or write back. .Ss Semantics This section describes the semantics of each operation using a C like notation. .Bl -hang @@ -281,15 +273,6 @@ functions are not implemented for the type The .Fn atomic_store functions are only provided with release memory barriers. -.\".Pp -.\"The type -.\".Dq Li 64 -.\"is currently not implemented for any of the atomic operations on the -.\".Tn arm , -.\".Tn i386 , -.\"and -.\".Tn powerpc -.\"architectures. .Sh RETURN VALUES The .Fn atomic_cmpset diff --git a/share/man/man9/bus_dma.9 b/share/man/man9/bus_dma.9 index 6235b135c4..50e7cef56a 100644 --- a/share/man/man9/bus_dma.9 +++ b/share/man/man9/bus_dma.9 @@ -389,7 +389,7 @@ may be specified for the tag intended to be used as the parent. must not be specified for the tags which will be used to create maps. For tags which will be used to create maps, -this argument must be less than 16384 on x86_64 and i386. +this argument must be less than 16384 on x86_64. .It Fa maxsegsz Maximum size, in bytes, of a segment in any DMA mapped region associated with diff --git a/share/man/man9/lwbuf.9 b/share/man/man9/lwbuf.9 index 129eafe566..6012292703 100644 --- a/share/man/man9/lwbuf.9 +++ b/share/man/man9/lwbuf.9 @@ -66,9 +66,7 @@ returns a pointer to a lightweight buffer representing The .Fa lwb argument is an lwbuf structure, used to avoid allocation of an lwbuf -on the x86_64 architecture. The -.Fa lwb -argument is unused on the i386 architecture. +on the x86_64 architecture. .Pp .Fn lwbuf_free frees all resources associated with the lightweight buffer @@ -96,12 +94,7 @@ It should not be used. The implementation of .Nm lwbuf is CPU-dependent. -On i386, pages taken from -per-processor pools of kernel virtual address space (KVA) are used to map -arbitrary -.Vt vm_page_t -objects. -On x86_64 such tricks are unnecessary, the +On x86_64 the kernel maintains a direct map of KVA covering all physical memory. .Pp Lightweight buffers are thread and cross-processor safe with a number of diff --git a/usr.bin/locate/locate/locate.1 b/usr.bin/locate/locate/locate.1 index da8365b739..9616b0d8e2 100644 --- a/usr.bin/locate/locate/locate.1 +++ b/usr.bin/locate/locate/locate.1 @@ -28,7 +28,6 @@ .\" .\" @(#)locate.1 8.1 (Berkeley) 6/6/93 .\" $FreeBSD: src/usr.bin/locate/locate/locate.1,v 1.16.2.5 2002/07/08 21:31:28 trhodes Exp $ -.\" $DragonFly: src/usr.bin/locate/locate/locate.1,v 1.4 2006/02/17 19:39:09 swildner Exp $ .\" .Dd June 6, 1993 .Dt LOCATE 1 @@ -252,7 +251,7 @@ The current implementation understand databases in host byte order or network byte order if both architectures use the same integer size. So you can read on a -.Dx Ns /i386 +.Dx Ns /x86_64 machine (little endian) a locate database which was built on SunOS/sparc machine diff --git a/usr.sbin/boot0cfg/boot0cfg.8 b/usr.sbin/boot0cfg/boot0cfg.8 index 1b0ec75802..d059343c28 100644 --- a/usr.sbin/boot0cfg/boot0cfg.8 +++ b/usr.sbin/boot0cfg/boot0cfg.8 @@ -46,7 +46,7 @@ The .Dx .Sq boot0 boot manager permits the operator to select from which disk and -slice an i386 machine (PC) is booted. +slice a PC is booted. .Pp Note that what are referred to here as .Dq slices diff --git a/usr.sbin/config/config.8 b/usr.sbin/config/config.8 index 0e941389eb..6fb8eae2ae 100644 --- a/usr.sbin/config/config.8 +++ b/usr.sbin/config/config.8 @@ -105,8 +105,8 @@ flag was specified, it will be removed first. The output of .Nm consists of a number of files; for the -.Tn i386 , -they are: +.Tn x86_64 +architecture, they are: .Pa ioconf.c , a description of what I/O devices are attached to the system; -- 2.11.4.GIT