From f5521f77ff660b570e1ca17b5fd3b39d5c683aaf Mon Sep 17 00:00:00 2001 From: bmah Date: Sun, 29 Jun 2003 01:10:45 +0000 Subject: Start to fill in amd64 hardware notes based on info from peter. Translators should be warned that this is somewhat of a moving target, and so might want to consider holding off working on this document. --- .../en_US.ISO8859-1/hardware/amd64/proc-amd64.sgml | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) (limited to 'release/doc') diff --git a/release/doc/en_US.ISO8859-1/hardware/amd64/proc-amd64.sgml b/release/doc/en_US.ISO8859-1/hardware/amd64/proc-amd64.sgml index 7b4aedf..56e8585 100644 --- a/release/doc/en_US.ISO8859-1/hardware/amd64/proc-amd64.sgml +++ b/release/doc/en_US.ISO8859-1/hardware/amd64/proc-amd64.sgml @@ -4,6 +4,25 @@ Supported Processors and Motherboards - We need to write this part. + &os;/&arch; has supported the &arch.print; + (Hammer) architecture since mid-2003. It made its + first debut as an experimental release based on &os; + 5.1-RELEASE. + + As of this writing, this port supports the Athlon64 + (Clawhammer) and Opteron + (Sledgehammer) machines. The largest tested + memory configuration to date is 8GB. There is no support for SMP + machines at present. + + In many respects, &os;/&arch; is similar to &os;/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. + + &os;/&arch; is still very much a work in progress. Much work + is being done in the &os; Perforce repository and then merged to + the &os; CVS repository as it stabilizes. -- cgit v1.1