From owner-freebsd-hackers  Sun Dec 14 03:08:22 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA28553
          for hackers-outgoing; Sun, 14 Dec 1997 03:08:22 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA28542
          for <freebsd-hackers@FreeBSD.ORG>; Sun, 14 Dec 1997 03:08:15 -0800 (PST)
          (envelope-from avalon@coombs.anu.edu.au)
Message-Id: <199712141108.DAA28542@hub.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA087377662; Sun, 14 Dec 1997 22:07:42 +1100
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: Beginning SPARC port
To: tlambert@primenet.com (Terry Lambert)
Date: Sun, 14 Dec 1997 22:07:41 +1100 (EDT)
Cc: jasone@canonware.com, jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199712130002.RAA17704@usr04.primenet.com> from "Terry Lambert" at Dec 13, 97 00:02:15 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Terry Lambert, sie said:
[...]
> Part of getting the kernel working is in doing a lot of hardware
> specific things.  These need to be abstracted (this is my opinion)
> to make ports easier.  I think these should be encapsulated via a
> C interface, so that for a new port, you can write a C stub that
> provides the hardware specific information as hardcoded values for
> the porting hardware you are using.  Memory size, etc..  All the
> things you would get from PPCBug, M68kBug, OpenBoot, PC BIOS, etc..
> I would be happy to help with this code.

I hate to say this, but, see NetBSD.