From owner-freebsd-embedded@FreeBSD.ORG Fri Jun 30 10:50:11 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 AABB616A403 for ; Fri, 30 Jun 2006 10:50:11 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EA5D43D45 for ; Fri, 30 Jun 2006 10:50:11 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 8229746CFC; Fri, 30 Jun 2006 06:50:10 -0400 (EDT) Date: Fri, 30 Jun 2006 11:50:10 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: embedded@FreeBSD.org Message-ID: <20060630114807.S3964@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Aditya Godbole 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: Fri, 30 Jun 2006 10:50:11 -0000 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. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Fri, 30 Jun 2006 12:07:56 +0530 From: Aditya Godbole To: freebsd-hackers@freebsd.org Subject: Re: New architecture support On 6/27/06, John Baldwin wrote: > > If I have to add support for a new architecture, how do I start? > > Well, you'll need a toolchain. :) Then you can start working on building > a minimal kernel filling in missing bits in sys/ as you go. Is there any documentation regarding the interface between the machine independant and machine dependant parts of the kernel. Also what functionality does the machine independant part expect to be in place? -aditya _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-embedded@FreeBSD.ORG Fri Jun 30 15:17:04 2006 Return-Path: X-Original-To: freebsd-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 7F03416A407; Fri, 30 Jun 2006 15:17:04 +0000 (UTC) (envelope-from gonzo@pbxpress.com) Received: from mail.portaone.com (mail.portaone.com [65.61.200.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EAE543D46; Fri, 30 Jun 2006 15:17:03 +0000 (GMT) (envelope-from gonzo@pbxpress.com) Received: from dell.portaone.com (unknown [70.68.128.186]) by mail.portaone.com (Postfix) with ESMTP id AD390552C21; Fri, 30 Jun 2006 08:17:03 -0700 (PDT) Received: from leaf.pbxpress.com (www.pbxpress.com [142.179.71.212]) by dell.portaone.com (8.13.6/8.13.1) with ESMTP id k5UFH36Z038165; Fri, 30 Jun 2006 08:17:03 -0700 (PDT) (envelope-from gonzo@pbxpress.com) Received: from [10.0.0.199] (tavex.colocall.com [62.149.10.42]) (authenticated bits=0) by leaf.pbxpress.com (8.13.3/8.13.3) with ESMTP id k5UFHsEB061762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jun 2006 08:18:02 -0700 (PDT) (envelope-from gonzo@pbxpress.com) Message-ID: <44A54061.8090102@pbxpress.com> Date: Fri, 30 Jun 2006 18:16:49 +0300 From: Oleksandr Tymoshenko User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.2 required=5.0 tests=AWL autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on leaf.pbxpress.com Cc: jmallet@freebsd.org, freebsd-mips@freebsd.org Subject: MIPS32 support 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: Fri, 30 Jun 2006 15:17:04 -0000 Hello people. For last few weekends I've been tweaking code of latest freebsd-mips snapshot, provided by Juli, intending to run it on MIPS32 evaluation board I'd got. On the moment I have some low-level stuff ported: TLB handling, traps handling, interrupt handling. Kernel boots and runs on a board(well, till a certain moment of course, there is no PCI bus support yet). Not many changes to original code, but it took a while to look through architecture specs. Now, when I know where to go further with porting, I'd like to put my changes together, clean them out and keep in sync with main development branch. The latest available sources are more then one year old. Was there any progress since then? Also there is a question of keeping mips64/mips32 sources together. NetBSD keeps code for both platforms as one meta-architecture "mips" and manage it with #defines from architectures like "evbmips". It's only mips64 tree in the snapshot so far. So I wander if there is a kind of roadmap for freebsd-mips project. Thanks! -- gonzo 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 From owner-freebsd-embedded@FreeBSD.ORG Sat Jul 1 08:54:46 2006 Return-Path: X-Original-To: freebsd-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 1FD9616A403; Sat, 1 Jul 2006 08:54:46 +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 C550B441BE; Sat, 1 Jul 2006 08:54:45 +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 k618sIAf042644; Sat, 1 Jul 2006 01:54:18 -0700 (PDT) Date: Sat, 01 Jul 2006 17:54:15 +0900 Message-ID: From: gnn@freebsd.org To: Oleksandr Tymoshenko In-Reply-To: <44A54061.8090102@pbxpress.com> References: <44A54061.8090102@pbxpress.com> 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: jmallet@freebsd.org, freebsd-embedded@freebsd.org, freebsd-mips@freebsd.org Subject: Re: MIPS32 support 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:54:46 -0000 At Fri, 30 Jun 2006 18:16:49 +0300, Oleksandr Tymoshenko wrote: > > So I wander if there is a kind of roadmap for freebsd-mips > project. Thanks! Having a working model is the first step, and it looks like you're getting there. If you have any special documentation on how to build this system please let me know URLs or docs and I'll put them up on embeddedfreebsd.org Thanks, George