From owner-p4-projects@FreeBSD.ORG Fri Oct 10 15:05:47 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id AFC081065696; Fri, 10 Oct 2008 15:05:47 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72AAA1065689 for ; Fri, 10 Oct 2008 15:05:47 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 5CE368FC13 for ; Fri, 10 Oct 2008 15:05:47 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id m9AF5lvR070242 for ; Fri, 10 Oct 2008 15:05:47 GMT (envelope-from pgj@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id m9AF5krf070240 for perforce@freebsd.org; Fri, 10 Oct 2008 15:05:46 GMT (envelope-from pgj@FreeBSD.org) Date: Fri, 10 Oct 2008 15:05:46 GMT Message-Id: <200810101505.m9AF5krf070240@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to pgj@FreeBSD.org using -f From: Gabor Pali To: Perforce Change Reviews Cc: Subject: PERFORCE change 151218 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2008 15:05:47 -0000 http://perforce.freebsd.org/chv.cgi?CH=151218 Change 151218 by pgj@kolbasz on 2008/10/10 15:05:33 IFC Affected files ... .. //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/authors.ent#15 integrate .. //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent#7 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/faq/book.sgml#25 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/Makefile#5 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/basics/chapter.sgml#5 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/book.sgml#8 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/chapters.ent#5 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/disks/chapter.sgml#7 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/eresources/chapter.sgml#14 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/geom/chapter.sgml#7 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/mirrors/chapter.sgml#15 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/network-servers/chapter.sgml#13 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/ports/chapter.sgml#9 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/security/chapter.sgml#14 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/share/sgml/mailing-lists.ent#15 integrate .. //depot/projects/docproj_hu/doc/share/images/articles/releng/branches-releng6.pic#2 integrate .. //depot/projects/docproj_hu/doc/share/images/articles/releng/branches-releng7.pic#1 branch .. //depot/projects/docproj_hu/doc/share/sgml/man-refs.ent#9 integrate .. //depot/projects/docproj_hu/src/release/doc/en_US.ISO8859-1/hardware/article.sgml#4 integrate .. //depot/projects/docproj_hu/src/release/doc/en_US.ISO8859-1/relnotes/article.sgml#7 integrate .. //depot/projects/docproj_hu/src/release/doc/share/misc/man2hwnotes.pl#2 integrate .. //depot/projects/docproj_hu/src_7/release/doc/en_US.ISO8859-1/relnotes/article.sgml#4 integrate .. //depot/projects/docproj_hu/www/en/cgi/getmsg.cgi#2 integrate .. //depot/projects/docproj_hu/www/en/developers.sgml#13 integrate .. //depot/projects/docproj_hu/www/en/releases/6.4R/schedule.sgml#6 integrate .. //depot/projects/docproj_hu/www/en/releng/index.sgml#7 integrate .. //depot/projects/docproj_hu/www/en/relnotes.sgml#2 integrate .. //depot/projects/docproj_hu/www/en/relnotes/Makefile#2 integrate .. //depot/projects/docproj_hu/www/share/sgml/news.xml#22 integrate .. //depot/projects/docproj_hu/www/share/sgml/press.xml#8 integrate Differences ... ==== //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/authors.ent#15 (text+ko) ==== @@ -13,7 +13,7 @@ builds for the other languages, and we will poke fun of you in public. - $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.462 2008/09/18 14:20:54 zec Exp $ + $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.463 2008/10/06 08:36:30 lstewart Exp $ --> aaron@FreeBSD.org"> @@ -624,6 +624,8 @@ logo@FreeBSD.org"> +lstewart@FreeBSD.org"> + lth@FreeBSD.org"> luigi@FreeBSD.org"> ==== //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -395,9 +395,53 @@ FreeBSD sun4v porting mailing list"> freebsd-sun4v"> - -FreeBSD SVN src commit list"> -svn-src"> + +SVN commit messages for the entire src tree (except for user and projects)"> +svn-src-all"> + + +SVN commit messages for the src tree for head/-current"> +svn-src-head"> + + +SVN commit messages for the src projects tree"> +svn-src-projects"> + + +SVN commit messages for releases in the src tree"> +svn-src-release"> + + +SVN commit messages for the release engineering / security commits to the src tree"> +svn-src-releng"> + + +SVN commit messages for all the -stable branches of the src tree"> +svn-src-stable"> + + +SVN commit messages for only the 6-stable src tree"> +svn-src-stable-6"> + + +SVN commit messages for only the 7-stable src tree"> +svn-src-stable-7"> + + +SVN commit messages for the old stable src trees"> +svn-src-stable-other"> + + +SVN commit messages for the admin / configuration tree"> +svn-src-svnadmin"> + + +SVN commit messages for the experimental user src tree"> +svn-src-user"> + + +SVN commit messages for the vendor work area tree"> +svn-src-vendor"> FreeBSD test mailing list"> ==== //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/faq/book.sgml#25 (text+ko) ==== @@ -20,7 +20,7 @@ A &os; Dokumentációs Projekt - $FreeBSD: doc/hu_HU.ISO8859-2/books/faq/book.sgml,v 1.2 2008/09/06 15:11:08 pgj Exp $ + $FreeBSD: doc/hu_HU.ISO8859-2/books/faq/book.sgml,v 1.3 2008/10/05 01:34:24 pgj Exp $ 1995 ==== //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/Makefile#5 (text+ko) ==== @@ -2,7 +2,7 @@ # The FreeBSD Documentation Project # The FreeBSD Hungarian Documentation Project -# $FreeBSD: doc/hu_HU.ISO8859-2/books/handbook/Makefile,v 1.2 2008/06/25 11:28:04 gabor Exp $ +# $FreeBSD: doc/hu_HU.ISO8859-2/books/handbook/Makefile,v 1.3 2008/10/05 01:34:24 pgj Exp $ # %SOURCE% en_US.ISO8859-1/books/handbook/Makefile # %SRCID% 1.110 # ==== //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/basics/chapter.sgml#5 (text+ko) ==== @@ -1,7 +1,7 @@ ==== //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/disks/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -3249,6 +3249,7 @@ + @@ -3410,6 +3411,7 @@ + ==== //depot/projects/docproj_hu/src/release/doc/en_US.ISO8859-1/hardware/article.sgml#4 (text+ko) ==== @@ -12,1390 +12,1592 @@ ]>
+ + &os; &release.current; Hardware Notes + + The &os; Documentation Project - - &os; &release.current; Hardware Notes + $FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/article.sgml,v 1.339 2008/10/06 21:52:11 simon Exp $ + + + 2000 + 2001 + 2002 + 2003 + 2004 + 2005 + 2006 + 2007 + 2008 + The &os; Documentation Project + + + + &tm-attrib.freebsd; + &tm-attrib.amd; + &tm-attrib.ibm; + &tm-attrib.intel; + &tm-attrib.sparc; + &tm-attrib.sun; + &tm-attrib.general; + - The &os; Documentation Project + - $FreeBSD: src/release/doc/en_US.ISO8859-1/hardware/article.sgml,v 1.333 2008/10/04 15:41:25 simon Exp $ + + Introduction - - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - The &os; Documentation Project - + This document contains the hardware compatibility notes for + &os; &release.current;. It lists the hardware platforms + supported by &os;, as well as the various types of hardware + devices (storage controllers, network interfaces, and so on), + along with known working instances of these devices. + - - &tm-attrib.freebsd; - &tm-attrib.amd; - &tm-attrib.ibm; - &tm-attrib.intel; - &tm-attrib.sparc; - &tm-attrib.sun; - &tm-attrib.general; - + + Supported Processors and System Boards - + This section provides some architecture-specific information + about the specific processors and systems that are supported by + each architecture. - - Introduction + + amd64 - This document contains the hardware compatibility notes for - &os; &release.current;. - It lists the hardware platforms supported by &os;, as well as the - various types of hardware devices (storage controllers, network - interfaces, and so on), along with known working instances of these - devices. + Since mid-2003 &os;/&arch.amd64; has supported the AMD64 + (Hammer) and &intel; EM64T architecture, and is + now one of the Tier-1 platforms (fully supported + architecture), which are expected to be Production Quality + with respects to all aspects of the &os; operating system, + including installation and development environments. - + Note that there are two names for this architecture, AMD64 + (AMD) and Intel EM64T (Extended Memory 64-bit Technology). + 64-bit mode of the two architectures are almost compatible + with each other, and &os;/&arch.amd64; should support them + both. - - Supported Processors and System Boards + As of this writing, the following processors are + supported: - This section provides some architecture-specific information - about the specific processors and systems that are supported by - each architecture. + + + &amd.athlon;64 (Clawhammer). + - - amd64 + + &amd.opteron; (Sledgehammer). + - Since mid-2003 &os;/&arch.amd64; has supported the AMD64 - (Hammer) and &intel; EM64T architecture, - and is now one of the Tier-1 platforms (fully - supported architecture), which are expected to be Production - Quality with respects to all aspects of the &os; operating system, - including installation and development environments. + + &intel; 64-bit &xeon; (Nacona). This + processor is fabricated on 90nm process technology, and + operates with 2.80 to 3.60 GHz (FSB 800MHz) and &intel; + E7520/E7525/E7320 chipsets. + - Note that there are two names for this architecture, - AMD64 (AMD) and Intel EM64T (Extended Memory 64-bit Technology). - 64-bit mode of the two architectures are almost compatible - with each other, and &os;/&arch.amd64; should support them both. + + &intel; &pentium; 4 Processor supporting &intel; EM64T + (Prescott). This is fabricated on 90nm + process technology, uses FC-LGA775 package, and operates + with 3.20F/3.40F/3.60F GHz and &intel; 925X Express + chipsets. The corresponding S-Spec numbers are SL7L9, + SL7L8, SL7LA, SL7NZ, SL7PZ, and SL7PX. Note that + processors marked as 5xx numbers do not support + EM64T. + + - As of this writing, the following processors are - supported: + &intel; EM64T is an extended version of IA-32 (x86) and + different from &intel; IA-64 (Itanium) architecture, which + &os;/ia64 supports. Some &intel;'s old documentation refers + to &intel; EM64T as 64-bit extension technology + or IA-32e. - - - &amd.athlon;64 (Clawhammer). - + The largest tested memory configuration to date is 8GB. + SMP support has been recently completed and is reasonably + robust. - - &amd.opteron; (Sledgehammer). - + In many respects, &os;/&arch.amd64; is similar to + &os;/&arch.i386;, in terms of drivers supported. There may be + some issues with 64-bit cleanliness in some (particularly + older) drivers. Generally, drivers that already function + correctly on other 64-bit platforms should work. - - &intel; 64-bit &xeon; (Nacona). - This processor is fabricated on 90nm process technology, and operates - with 2.80 to 3.60 GHz (FSB 800MHz) and &intel; E7520/E7525/E7320 chipsets. - + &os;/&arch.amd64; is a very young platform on &os;. While + the core &os; kernel and base system components are generally + fairly robust, there are likely to still be rough edges, + particularly with third party packages. - - &intel; &pentium; 4 Processor supporting &intel; EM64T - (Prescott). - This is fabricated on 90nm process technology, - uses FC-LGA775 package, and operates with 3.20F/3.40F/3.60F GHz - and &intel; 925X Express chipsets. - The corresponding S-Spec numbers are SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ, - and SL7PX. Note that processors marked as 5xx numbers do not support - EM64T. - - + - &intel; EM64T is an extended version of IA-32 (x86) and - different from &intel; IA-64 (Itanium) architecture, which &os;/ia64 - supports. Some &intel;'s old documentation refers to &intel; EM64T as - 64-bit extension technology or IA-32e. + + i386 - The largest tested - memory configuration to date is 8GB. SMP support has been - recently completed and is reasonably robust. + &os;/&arch.i386; runs on a wide variety of IBM PC + compatible machines. Due to the wide range of + hardware available for this architecture, it is impossible + to exhaustively list all combinations of equipment supported + by &os;. Nevertheless, some general guidelines are + presented here. - In many respects, &os;/&arch.amd64; is similar to &os;/&arch.i386;, in - terms of drivers supported. There may be some issues with 64-bit - cleanliness in some (particularly older) drivers. Generally, - drivers that already function correctly on other 64-bit platforms - should work. + Almost all &i386;-compatible processors with a floating + point unit are supported. All &intel; processors beginning + with the 80486 are supported, including the 80486, &pentium;, + &pentium; Pro, &pentium; II, &pentium; III, &pentium; 4, and + variants thereof, such as the &xeon; and &celeron; processors. + All &i386;-compatible AMD processors are also supported, + including the &am486;, &am5x86;, K5, &amd.k6; (and variants), + &amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, and + Athlon Thunderbird), and &amd.duron; processors. The AMD + Élan SC520 embedded processor is supported. The + Transmeta Crusoe is recognized and supported, as are + &i386;-compatible processors from Cyrix and NexGen. - &os;/&arch.amd64; is a very young platform on &os;. While the - core &os; kernel and base system components are generally - fairly robust, there are likely to still be rough edges, - particularly with third party packages. + There is a wide variety of motherboards available for this + architecture. Motherboards using the ISA, VLB, EISA, AGP, and + PCI expansion busses are well-supported. There is some + limited support for the MCA (MicroChannel) + expansion bus used in the IBM PS/2 line of PCs. - + Symmetric multi-processor (SMP) systems are generally + supported by &os;, although in some cases, BIOS or motherboard + bugs may generate some problems. Perusal of the archives of + the &a.smp; may yield some clues. - - i386 + &os; will take advantage of HyperThreading (HTT) support + on &intel; CPUs that support this feature. A kernel with the + options SMP feature enabled will + automatically detect the additional logical processors. The + default &os; scheduler treats the logical processors the same + as additional physical processors; in other words, no attempt + is made to optimize scheduling decisions given the shared + resources between logical processors within the same CPU. + Because this naive scheduling can result in suboptimal + performance, under certain circumstances it may be useful to + disable the logical processors with the the + machdep.hlt_logical_cpus sysctl variable. + It is also possible to halt any CPU in the idle loop with the + machdep.hlt_cpus sysctl variable. The + &man.smp.4; manual page has more details. - &os;/&arch.i386; runs on a wide variety of IBM PC - compatible machines. Due to the wide range of hardware - available for this architecture, it is impossible to exhaustively - list all combinations of equipment supported by &os;. - Nevertheless, some general guidelines are presented here. + &os; will take advantage of Physical Address Extensions + (PAE) support on CPUs that support this feature. A kernel + with the PAE feature enabled will detect + memory above 4 gigabytes and allow it to be used by the + system. This feature places constraints on the device drivers + and other features of &os; which may be used; consult the + &man.pae.4; manpage for more details. - Almost all &i386;-compatible processors with a floating point unit - are supported. All - &intel; processors beginning with the 80486 are supported, including - the 80486, &pentium;, &pentium; Pro, &pentium; II, &pentium; III, - &pentium; 4, and variants thereof, such as the &xeon; and &celeron; - processors. All &i386;-compatible AMD - processors are also supported, including the &am486;, &am5x86;, K5, &amd.k6; - (and variants), &amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, - and Athlon Thunderbird), and &amd.duron; processors. The AMD - Élan SC520 embedded processor is supported. The Transmeta - Crusoe is recognized and supported, as are &i386;-compatible - processors from Cyrix and NexGen. + &os; will generally run on i386-based laptops, albeit with + varying levels of support for certain hardware features such + as sound, graphics, power management, and PCCARD expansion + slots. These features tend to vary in idiosyncratic ways + between machines, and frequently require special-case support + in &os; to work around hardware bugs or other oddities. When + in doubt, a search of the archives of the &a.mobile; may be + useful. - There is a wide variety of motherboards available for this - architecture. Motherboards using the ISA, VLB, EISA, AGP, and PCI - expansion busses are well-supported. There is some limited - support for the MCA (MicroChannel) expansion bus - used in the IBM PS/2 line of PCs. + Most modern laptops (as well as many desktops) use the + Advanced Configuration and Power Management (ACPI) standard. + &os; supports ACPI via the ACPI Component Architecture + reference implementation from &intel;, as described in the + &man.acpi.4; manual page. The use of ACPI causes + instabilities on some machines and it may be necessary to + disable the ACPI driver, which is normally loaded via a kernel + module. This may be accomplished by adding the following line + to /boot/device.hints: - Symmetric multi-processor (SMP) systems are generally - supported by &os;, although in some cases, BIOS or motherboard - bugs may generate some problems. Perusal of the archives of the - &a.smp; may yield some clues. + hint.acpi.0.disabled="1" - &os; will take advantage of HyperThreading (HTT) support on - &intel; CPUs that support this feature. A kernel with the - options SMP feature enabled will - automatically detect the additional logical processors. The - default &os; scheduler treats the logical processors the same as - additional physical processors; in other words, no attempt is made - to optimize scheduling decisions given the shared resources - between logical processors within the same CPU. Because this - naive scheduling can result in suboptimal performance, under - certain circumstances it may be useful to disable the logical - processors with the - the machdep.hlt_logical_cpus sysctl variable. - It is also possible to halt any CPU in the idle loop with the - machdep.hlt_cpus sysctl variable. The - &man.smp.4; manual page has more details. + Users debugging ACPI-related problems may find it useful + to disable portions of the ACPI functionality. The + &man.acpi.4; manual page has more information on how to do + this via loader tunables. - &os; will take advantage of Physical Address Extensions (PAE) - support on CPUs that support this feature. A kernel with the - PAE feature enabled will detect memory above - 4 gigabytes and allow it to be used by the system. This feature - places constraints on the device drivers and other features of - &os; which may be used; consult the &man.pae.4; manpage for more - details. + ACPI depends on a Differentiated System Descriptor Table + (DSDT) provided by each machine's BIOS. Some machines have + bad or incomplete DSDTs, which prevents ACPI from functioning + correctly. Replacement DSDTs for some machines can be found + at the DSDT + section of the ACPI4Linux project + Web site. &os; can use these DSDTs to override the DSDT + provided by the BIOS; see the &man.acpi.4; manual page for + more information. + - &os; will generally run on i386-based laptops, albeit with - varying levels of support for certain hardware features such as - sound, graphics, power management, and PCCARD expansion slots. - These features tend to vary in idiosyncratic ways between - machines, and frequently require special-case support in &os; to - work around hardware bugs or other oddities. When in doubt, a - search of the archives of the &a.mobile; may be useful. + + ia64 - Most modern laptops (as well as many desktops) use the - Advanced Configuration and Power Management (ACPI) standard. &os; - supports ACPI via the ACPI Component Architecture reference - implementation from &intel;, as described in the &man.acpi.4; manual - page. The use of ACPI causes instabilities on some machines and it - may be necessary to disable the ACPI driver, which is normally - loaded via a kernel module. This may be accomplished by adding - the following line to /boot/device.hints: + Currently supported processors are the &itanium; + and the &itanium; + 2. - hint.acpi.0.disabled="1" + Supported chipsets include: - Users debugging ACPI-related problems may find it useful to - disable portions of the ACPI functionality. The &man.acpi.4; - manual page has more information on how to do this via loader - tunables. + + + HP zx1 + - ACPI depends on a Differentiated System Descriptor Table - (DSDT) provided by each machine's BIOS. Some machines have bad or - incomplete DSDTs, which prevents ACPI from functioning correctly. - Replacement DSDTs for some machines can be found at the DSDT - section of the ACPI4Linux project Web - site. &os; can use these DSDTs to override the DSDT provided by - the BIOS; see the &man.acpi.4; manual page for more - information. - + + &intel; 460GX + - - ia64 + + &intel; E8870 + + - Currently supported processors are the - - &itanium; and the - - &itanium; 2. + Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) + configurations are supported. - Supported chipsets include: - - - HP zx1 - - - &intel; 460GX - - - &intel; E8870 - - + Most devices that can be found in or are compatible with + &arch.ia64; machines are fully supported. The notable + exception is the VGA console. The &os; support for VGA + consoles is at this time too much based on PC hardware and not + all &arch.ia64; machines have chipsets that provide sufficient + PC legacy support. As such &man.syscons.4; can not be enabled + and the use of a serial console is required. + - Both Uniprocessor (UP) and Symmetric Multi-processor (SMP) - configurations are supported. + + pc98 - Most devices that can be found in or are compatible with - &arch.ia64; machines are fully supported. The notable exception - is the VGA console. The &os; support for VGA consoles is at - this time too much based on PC hardware and not all &arch.ia64; - machines have chipsets that provide sufficient PC legacy - support. As such &man.syscons.4; can not be enabled and the - use of a serial console is required. + NEC PC-9801/9821 series with almost all &i386;-compatible + processors, including 80486, &pentium;, &pentium; Pro, + &pentium; II, and variants. All &i386;-compatible processors + by AMD, Cyrix, IBM, and IDT are also supported. - + NEC FC-9801/9821 series, and NEC SV-98 series (both of + them are compatible with PC-9801/9821 series) should be + supported. - - pc98 + EPSON PC-386/486/586 series, which are compatible with NEC + PC-9801 series are supported. - NEC PC-9801/9821 series with almost all &i386;-compatible processors, - including 80486, &pentium;, &pentium; Pro, &pentium; II, and variants. - All &i386;-compatible processors by AMD, Cyrix, IBM, and IDT - are also supported. + High-resolution mode is not supported. NEC + PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in + normal (PC-9801 compatible) mode only. - NEC FC-9801/9821 series, and NEC SV-98 series - (both of them are compatible with PC-9801/9821 series) - should be supported. + Although there are some multi-processor systems (such as + Rs20/B20), SMP-related features of &os; are not supported + yet. - EPSON PC-386/486/586 series, which are - compatible with NEC PC-9801 series are supported. + PC-9801/9821 standard bus (called C-Bus), PC-9801NOTE + expansion bus (110pin), and PCI bus are supported. New Extend + Standard Architecture (NESA) bus (used in PC-H98, SV-H98, and + FC-H98 series) is not supported. + - High-resolution mode is not supported. - NEC PC-98XA/XL/RL/XL^2, and NEC PC-H98 series - are supported in normal (PC-9801 compatible) mode only. + + powerpc - Although there are some multi-processor systems - (such as Rs20/B20), SMP-related features of &os; - are not supported yet. + The information for this paragraph has yet to be + compiled. + - PC-9801/9821 standard bus (called C-Bus), - PC-9801NOTE expansion bus (110pin), - and PCI bus are supported. - New Extend Standard Architecture (NESA) bus - (used in PC-H98, SV-H98, and FC-H98 series) is not supported. + + sparc64 - + This section describes the systems currently known to be + supported by &os; on the &ultrasparc; platform. For + background information on the various hardware designs see the + Sun System + Handbook. - - powerpc + SMP is supported on all systems with more than 1 + processor. - The information for this paragraph has yet to be compiled. + In general, &os;/&arch.sparc64; systems must use serial + consoles. While it is possible to boot or install a system + using the OpenFirmware console, the console device is not + usable. - + If you have a system that is not listed here, it may not + have been tested with &os; &release.current;. We encourage + you to try it and send a note to the &a.sparc; with your + results, including which devices work and which do not. - - sparc64 + The following systems are fully supported by &os;. - This section describes the systems currently known to be supported - by &os; on the &ultrasparc; platform. For background information on the - various hardware designs see the Sun System Handbook. + + + &sun.blade; 100 + - SMP is supported on all systems with more than 1 processor. + + &sun.blade; 150 + - In general, &os;/&arch.sparc64; systems must use serial consoles. - While it is possible to boot or install a system using the - OpenFirmware console, the console device is not usable. + + &sun.enterprise; 220R + - If you have a system that is not listed here, it may not have - been tested with &os; &release.current;. We encourage you to - try it and send a note to the &a.sparc; with your results, - including which devices work and which do not. + + &sun.enterprise; 250 + - The following systems are fully supported by &os;. + + &sun.enterprise; 420R + - - - &sun.blade; 100 - - - &sun.blade; 150 - - - &sun.enterprise; 220R - - - &sun.enterprise; 250 - - - &sun.enterprise; 420R - &sun.enterprise; 450 - - &sun.fire; V100 - - - &sun.fire; V120 - - - &netra; t1 105 - - - &netra; T1 AC200/DC200 - - - &netra; t 1100 - - - &netra; t 1120 - - - &netra; t 1125 - - - &netra; t 1400/1405 - - - &netra; 120 - - - &netra; X1 - - - &sparcengine; Ultra AXi - - - &sparcengine; Ultra AXmp - - - &sun.ultra; 1 - - - &sun.ultra; 1E - - - &sun.ultra; 2 - - - &sun.ultra; 5 - - - &sun.ultra; 10 - >>> TRUNCATED FOR MAIL (1000 lines) <<<