This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--PEIAKu/WMn1b1Hv9
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.NEB.4.44.0202041447112.153@odysseus.mono.org>
Content-Disposition: INLINE

On Mon, 4 Feb 2002, Jan Schaumann wrote:

> David Brownlee <abs@netbsd.org> wrote:
> > On Sun, 3 Feb 2002, Jan Schaumann wrote:
>
> > > Other parts that mention NetBSD/foo are linked to "../Ports/foo/", and I
> > > thought it should link *somewhere* for consistency's sake.
> >
> > 	Sounds reasonable - could you add a brief paragraph to
> > 	Ports/index.html along the lines of:
>
> Ok, took your paragraph and put it on Ports/index.html#suggested-mips
> (see attached patch) - then we can link from contrib/hardware.html to
> #suggested-mips...

	Looks good.

-- 
		David/absolute		-- www.netbsd.org: No hype required --


--PEIAKu/WMn1b1Hv9
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-ID: <Pine.NEB.4.44.0202041447113.153@odysseus.mono.org>
Content-Description: 
Content-Disposition: ATTACHMENT; FILENAME="ports.diff"

Index: index.html
===================================================================
RCS file: /cvsroot/htdocs/Ports/index.html,v
retrieving revision 1.205
diff -u -r1.205 index.html
--- index.html	2001/12/31 12:01:09	1.205
+++ index.html	2002/02/04 14:40:20
@@ -727,6 +727,16 @@
 <p>
 <ul>
 
+<li>64-bit MIPS<br>
+	Many of the existing NetBSD/mips platforms are capable of running
+	64-bit code. A NetBSD/mips64 port would be similar to <a 
+	href="alpha/">NetBSD/alpha</a> with 64-bit longs and pointers and 32-bit
+	ints.
+	<p>
+    Contact: <a
+    href="mailto:port-mips@netbsd.org">port-mips@netbsd.org</a>.
+    <p>
+
 <li><a href="http://www.densan.com/">Densan</a><br>
     Densan produce a range of MIPS based <a
     href="http://www.densan.com/vme/vmeproducts.html">VME</a> and

--PEIAKu/WMn1b1Hv9--