From owner-freebsd-doc@FreeBSD.ORG Sat Dec 30 19:24:04 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7819016A417 for ; Sat, 30 Dec 2006 19:24:04 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.freebsd.org (Postfix) with ESMTP id 6280713C46B for ; Sat, 30 Dec 2006 19:24:04 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from [64.142.31.107] (tomcat.kitchenlab.org [64.142.31.107]) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id kBUJO3Ks032717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 30 Dec 2006 11:24:03 -0800 Message-ID: <4596BCCE.3030302@freebsd.org> Date: Sat, 30 Dec 2006 11:23:58 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.8 (X11/20061220) MIME-Version: 1.0 To: freebsd-doc@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig602CD9065AE9C9F25F4C7B55" Subject: RFC: Hardware notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Dec 2006 19:24:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig602CD9065AE9C9F25F4C7B55 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable About a month ago, I rearranged the hardware notes on CURRENT, in effect coalescing the multiple machine-dependent (MD) documents that got generated into a single machine-independent (MI) document. Basically it's easier to read and maintain this way. I'd like some review on a similar reorg of the hardware notes (also on CURRENT). The goal is pretty much the same, although it turns out this was a lot more work: o Each architecture has some MD sections, which I put into second-layer sections. o There are a *lot* more arch=3D attributes in the hardware notes (around= 80) than in the release notes. The conversion of these attributes is very mechanical but as far as I can tell is not easily automated. :-( o The auto-generated device listings (where device lists are pulled out of manpages) also handle the arch=3D attributes. I have a patch to modif= y this behavior in a halfway reasonable manner, although further hacking is needed (right now, we drop the second column of dev.archlist.txt into the hardware notes verbatim, but I'd really like to convert these to use the SGML entities I've defined for this). Also, as I'm reading through the hardware notes, there's a bunch of information (particular in the "supported processor and motherboards") section that could stand revising. That's probably best taken care of after this. Preliminary work is here: http://people.freebsd.org/~bmah/hardware2.tar.gz http://people.freebsd.org/~bmah/hardware2.pdf Comments greatly appreciated, particularly from those folks who have worked on the auto-generated device listings. Thanks and Happy New Year! Bruce. --------------enig602CD9065AE9C9F25F4C7B55 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFlrzT2MoxcVugUsMRAkrYAJ9UlWhtoIS8tdmjAXU6lXIe27nqJgCgi4Z0 /mURKpo/MSyWWRX7B+PuuzY= =amy1 -----END PGP SIGNATURE----- --------------enig602CD9065AE9C9F25F4C7B55--