Date: Wed, 24 Oct 2001 10:51:05 -0700 From: bmah@freebsd.org (Bruce A. Mah) To: freebsd-alpha@freebsd.org Cc: bmah@freebsd.org Subject: Alpha hardware notes Message-ID: <200110241751.f9OHp5Z17229@c527597-a.cstvl1.sfba.home.com>
index | next in thread | raw e-mail
[-- Attachment #1 --]
Hi alpha folks--
With the recent ia64 progress, I'm trying to figure out how to best
support more than two architectures in the release documentation. The
biggest headache is going to be the hardware notes...specifically the
lists of all the NICs, disk controllers, and other devices.
One thing I'd like to do is to figure out what to do with all of the
devices for which no explicitly-supported architecture(s) are listed.
In other words, does:
<para>foobar device (&man.foo.4; driver)</para>
really mean:
<para arch="i386,alpha">foobar device (&man.foo.4; driver)</para>
("it works on both the i386 and alpha") or does it really mean:
<para arch="i386">foobar device (&man.foo.4; driver)</para>
("it works on the i386, no one's tried it on the alpha")?
I'm not sure how to go about doing this, given that the only alpha
machine I can even login to is beast. One thing I thought of was to
make a pass through the GENERIC kernel configuration on a FreeBSD/alpha
machine and mark all drivers mentioned there as being explicitly
supported, then taking everything that's left and marking it as
i386-only.
Clearly this isn't perfect. Any ideas on how I can do this better?
Thanks!
Bruce.
PS. Right now I'm mostly concerned with -CURRENT...4-STABLE will
never have more than 2 architectures, so it's less of a problem
although anything that's MFC-able, should be.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: Exmh version 2.3.1+ 05/14/2001
iD8DBQE71v+J2MoxcVugUsMRAjAiAKCixPcrJyNXWrcJmvxuVc4gflLKhwCg0xzX
d/XSSQ+fx3c/r+SfVmfzTAs=
=hO8E
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110241751.f9OHp5Z17229>