From owner-freebsd-arm@FreeBSD.ORG Tue May 19 20:04:50 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9380F106567E for ; Tue, 19 May 2009 20:04:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5235C8FC16 for ; Tue, 19 May 2009 20:04:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n4JK2owF040776; Tue, 19 May 2009 14:02:50 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 19 May 2009 14:02:58 -0600 (MDT) Message-Id: <20090519.140258.1756924732.imp@bsdimp.com> To: chuckr@telenix.org From: "M. Warner Losh" In-Reply-To: <4A12D46B.8040808@telenix.org> References: <4A12D46B.8040808@telenix.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: crosscompiler and porting notes X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 20:04:51 -0000 In message: <4A12D46B.8040808@telenix.org> Chuck Robey writes: : First, for the processor OMAP3530 (the Cortex), is it possible to : use the llvm/clang compiler? Or, is gcc the compiler being used, : for cross compiling? What sources are being used? If it's the same : gcc in sources, then I need to know what are the flags used to build : with (or, if it's actually in the build already, where is it, how to : do that? The in-tree compiler currently is gcc/binutils, which we use for all ARM builds. I don't know if it has the newer ARM instructions for the OMAP3530. : 2nd question, is there any document, set of notes, anything at all, : to give any sort of info at all so that I might have some idea of : what needs to be changed in the kernel sources. I figure it's : probably not going to be anything like a complete document, but I'm : quite willing to try to use any level of document that might exist. : Understand, I *don't* want some general purpose porting guide : (something that would be used to create a bsd.port.mk-type port, I : need this to be specific for the kernel sources. No. You have to read the source to get this information at the present time. : As far as that goes, are all the sources for the current level of : work on the arm ports in the svn repository, or if it's somewhere : else, where might that be? Most of the work is in head. However, there's some still straggling in from the p4 //depot/projects/arm tree and I think we may have created a base/projects/arm tree in svn as well, but I'm not sure about that. Warner