Date: Sun, 10 Nov 2002 12:13:40 -0800 From: bmah@freebsd.org (Bruce A. Mah) To: Thomas Moestl <tmoestl@gmx.net> Cc: "Bruce A. Mah" <bmah@freebsd.org>, freebsd-sparc@freebsd.org, freebsd-doc@freebsd.org Subject: Re: sparc64 release documentation Message-ID: <200211102013.gAAKDe28092807@intruder.bmah.org> In-Reply-To: <20021110143308.GB333@crow.dom2ip.de> References: <200211082100.gA8L0OMc019228@intruder.bmah.org> <20021110143308.GB333@crow.dom2ip.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-1026807352P Content-Type: text/plain; charset=us-ascii If memory serves me right, Thomas Moestl wrote: > On Fri, 2002/11/08 at 13:00:24 -0800, Bruce A. Mah wrote: > > Hi sparc-ers, > > > > I've been perusing the sparc64 release documentation, and it looks like > > there's a few things that can be updated. To wit: > > > > 1. The install documentation is kind of obsolete, now that there's a > > real, running sysinstall. I think the sequence of instructions is now > > much closer to what i386, alpha, and pc98 use, which means we can > > probably use the unified installation document for them now (with > > suitable customization). > > Agreed. I'd like to keep the the instructions to setup network booting > somewhere (not necessarily in the install documentation). OK. One thing I discovered, BTW, is that the installation document turns into a real mess when we try to support more than about two architectures. :-( I am not sure how to deal with this yet. > > 2. The hardware list probably could use some updating too, > > I'm working on this, but am not done yet (need to collect some more > models that have been reported as working). > > > but this might be a little more useful if we could also cut over to > > the unified hardware list. > > I think it would be better to have a separated list that only mentions > drivers that have been confirmed to work on sparc64 for now, since > there are a lot of drivers which do not yet use busdma or cannot > handle big-endian architectures yet. Sorry, I was unclear here. "Unified" meant that there's one SGML source file for all architectures. We use some conditional inclusion of text (kind of like #ifdef/#endif) to select things that should only be included for specific architectures. If I were to do this for the hardware list today, it would look something like this: http://people.freebsd.org/~bmah/doc/hardware-sparc64.pdf My first cut at modifying the install document would look like this (this is mostly a cut and paste from the existing sparc64-specific file): http://people.freebsd.org/~bmah/doc/installation-sparc64.pdf It's closer to reality, but not perfect. If we end up doing something different, these attempts are expendible. > > Is there any interest in helping me update these things? (I'm not a > > sparc64 person, BTW.) If so, I'll change the documentation files to use > > the regular hardware and installation documents and let people go at it. > > I can help with markup issues, if necessary, but I don't know much > > about this platform. > > I will try to help as time permits. I'm not sure I will be done in > time for DP2 though (if the anticipated release date is still November > 20). I've given up trying to predict when the release will be. :-) We'll have a much better idea once we can get DP2 out the door. Thanks! Bruce. --==_Exmh_-1026807352P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) Comment: Exmh version 2.5+ 20020506 iD8DBQE9zr3z2MoxcVugUsMRApK4AKCiIPlD1rKnTEDuKCpxnu0xVsiTZACgpU2y ulLWdtkoQQhTqm6UK34JWAc= =Enxe -----END PGP SIGNATURE----- --==_Exmh_-1026807352P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211102013.gAAKDe28092807>