From owner-freebsd-embedded@FreeBSD.ORG Sat Jul 1 08:53:55 2006 Return-Path: X-Original-To: embedded@freebsd.org Delivered-To: freebsd-embedded@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4DE316A403; Sat, 1 Jul 2006 08:53:55 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DE1F441C0; Sat, 1 Jul 2006 08:53:55 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id k618r558042361; Sat, 1 Jul 2006 01:53:05 -0700 (PDT) Date: Sat, 01 Jul 2006 17:53:02 +0900 Message-ID: From: gnn@freebsd.org To: Robert Watson In-Reply-To: <20060630114807.S3964@fledge.watson.org> References: <20060630114807.S3964@fledge.watson.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.6.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Aditya Godbole , embedded@freebsd.org Subject: Re: New architecture support (fwd) X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jul 2006 08:53:55 -0000 At Fri, 30 Jun 2006 11:50:10 +0100 (BST), rwatson wrote: > > > Since embedded is both driving (and reliant on) new architecture > support, does it make sense to create some documentation on what > hardware ports involve? I mean both "from scratch" and > "incremental". If someone has notes, I'm sure we could get some > help in converting it into a developer's handbook chapter or > article. Since new hardware ports for FreeBSD appear to be done > with moderate frequency, the knowledge is definitely out there. There are basically two improvements in our docs that would make things easier. Better "porting" docs and better "driver" docs. Geting basic driver support in a BSP (Board Support Package) is the key to getting a board up and running. If people have notes I can try to corral them. If people want to try updating the developers handbook without my corralling, even better. Later, George