From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 04:14:13 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B505816A412; Wed, 4 Oct 2006 04:14:13 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8048143D62; Wed, 4 Oct 2006 04:14:13 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 65160140EC01; Wed, 4 Oct 2006 03:55:33 +0000 (GMT) Date: Wed, 4 Oct 2006 03:55:33 +0000 From: John Birrell To: freebsd-ppc@freebsd.org, freebsd-arm@freebsd.org Message-ID: <20061004035533.GA76969@what-creek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 04:14:13 -0000 The patch: moves all the relocation definitions for each arch from the machine/elf.h header to sys/elf_common.h. This will allow DTrace running hosted on one FreeBSD arch connect to a target FreeBSD arch to trace it. Although this isn't functionality that Sun has in OpenSolaris, FreeBSD needs to support embedded targets. I have tested all the arches define in 'make universe', but it seems that PPC and ARM aren't up to that stage yet. Note that this patch also contains the extra things that Sun has added to their ELF format. I doubt this patch will cause any problems on either PPC or ARM. Any problems? -- John Birrell From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 15:51:49 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA44D16A415 for ; Wed, 4 Oct 2006 15:51:49 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDA6A43D68 for ; Wed, 4 Oct 2006 15:51:47 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so906717qbd for ; Wed, 04 Oct 2006 08:51:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=czD5Sig/4AoU9gjFI1LBf3h4fvjKGT0oZZDVyja5opc1hXJeVvEsnEw9y9B7WCvrwUZALhnBagjbI/RlsZ7GwoKn52Q0r0V8aKQmUfwnAo23Tm21or5xjp7lVcWIHKM+3RmF0BhKtLJG6yca0KhirxPpcsc0rqqTZDEEuIh21s4= Received: by 10.65.234.2 with SMTP id l2mr680573qbr; Wed, 04 Oct 2006 08:44:26 -0700 (PDT) Received: by 10.64.179.8 with HTTP; Wed, 4 Oct 2006 08:44:26 -0700 (PDT) Message-ID: <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> Date: Wed, 4 Oct 2006 21:14:26 +0530 From: "Joseph Koshy" To: "John Birrell" In-Reply-To: <20061004035533.GA76969@what-creek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061004035533.GA76969@what-creek.com> Cc: freebsd-arm@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 15:51:49 -0000 > The patch: moves > all the relocation definitions for each arch from the machine/elf.h > header to sys/elf_common.h. What's the semantic difference between an 'Lword' and an 'Xword'? + typedef uint64_t Elf32_Lword; and... typedef int32_t Elf64_Sword; typedef int64_t Elf64_Sxword; typedef uint32_t Elf64_Word; + typedef uint64_t Elf64_Lword; typedef uint64_t Elf64_Xword; /* -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 16:57:28 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E908516A412; Wed, 4 Oct 2006 16:57:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id F09B243D92; Wed, 4 Oct 2006 16:57:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k94Gtmi5014149; Wed, 4 Oct 2006 10:55:49 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 04 Oct 2006 10:54:41 -0600 (MDT) Message-Id: <20061004.105441.1649768370.imp@bsdimp.com> To: joseph.koshy@gmail.com From: "M. Warner Losh" In-Reply-To: <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> References: <20061004035533.GA76969@what-creek.com> <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 04 Oct 2006 10:55:51 -0600 (MDT) Cc: freebsd-arm@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 16:57:29 -0000 In message: <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> "Joseph Koshy" writes: : > The patch: moves : > all the relocation definitions for each arch from the machine/elf.h : > header to sys/elf_common.h. : : What's the semantic difference between an 'Lword' and an 'Xword'? : : + typedef uint64_t Elf32_Lword; : : and... : : typedef int32_t Elf64_Sword; : typedef int64_t Elf64_Sxword; : typedef uint32_t Elf64_Word; : + typedef uint64_t Elf64_Lword; : typedef uint64_t Elf64_Xword; : : /* What's the advantage of moving all the machine specific defines as well? Warner From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 20:17:22 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AED6F16A40F; Wed, 4 Oct 2006 20:17:22 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5A9A43D86; Wed, 4 Oct 2006 20:17:09 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id BE85A140EC01; Wed, 4 Oct 2006 20:17:06 +0000 (GMT) Date: Wed, 4 Oct 2006 20:17:06 +0000 From: John Birrell To: "M. Warner Losh" Message-ID: <20061004201706.GB82080@what-creek.com> References: <20061004035533.GA76969@what-creek.com> <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> <20061004.105441.1649768370.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061004.105441.1649768370.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org, joseph.koshy@gmail.com, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 20:17:22 -0000 On Wed, Oct 04, 2006 at 10:54:41AM -0600, M. Warner Losh wrote: > What's the advantage of moving all the machine specific defines as > well? So that one arch can host the DTrace client for another target arch. DTrace needs to understand the relocations, so it needs access to the defines for all arches, even though they are machine specific. -- John Birrell From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 20:20:12 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B3016A403; Wed, 4 Oct 2006 20:20:12 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDD1343D6B; Wed, 4 Oct 2006 20:20:07 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 0E0B5140EC03; Wed, 4 Oct 2006 20:20:05 +0000 (GMT) Date: Wed, 4 Oct 2006 20:20:04 +0000 From: John Birrell To: Joseph Koshy Message-ID: <20061004202004.GC82080@what-creek.com> References: <20061004035533.GA76969@what-creek.com> <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 20:20:12 -0000 On Wed, Oct 04, 2006 at 09:14:26PM +0530, Joseph Koshy wrote: > >The patch: moves > >all the relocation definitions for each arch from the machine/elf.h > >header to sys/elf_common.h. > > What's the semantic difference between an 'Lword' and an 'Xword'? > > + typedef uint64_t Elf32_Lword; > > and... > > typedef int32_t Elf64_Sword; > typedef int64_t Elf64_Sxword; > typedef uint32_t Elf64_Word; > + typedef uint64_t Elf64_Lword; > typedef uint64_t Elf64_Xword; I'm not sure there is any. It's just something that OpenSolaris code expects. -- John Birrell From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 21:27:28 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77DFD16A412; Wed, 4 Oct 2006 21:27:28 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79B9843D4C; Wed, 4 Oct 2006 21:27:23 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 2D68A140EC01; Wed, 4 Oct 2006 21:27:20 +0000 (GMT) Date: Wed, 4 Oct 2006 21:27:20 +0000 From: John Birrell To: Joseph Koshy Message-ID: <20061004212719.GA82760@what-creek.com> References: <20061004035533.GA76969@what-creek.com> <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> <20061004202004.GC82080@what-creek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061004202004.GC82080@what-creek.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM 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: Wed, 04 Oct 2006 21:27:28 -0000 On Wed, Oct 04, 2006 at 08:20:04PM +0000, John Birrell wrote: > On Wed, Oct 04, 2006 at 09:14:26PM +0530, Joseph Koshy wrote: > > >The patch: moves > > >all the relocation definitions for each arch from the machine/elf.h > > >header to sys/elf_common.h. > > > > What's the semantic difference between an 'Lword' and an 'Xword'? > > > > + typedef uint64_t Elf32_Lword; > > > > and... > > > > typedef int32_t Elf64_Sword; > > typedef int64_t Elf64_Sxword; > > typedef uint32_t Elf64_Word; > > + typedef uint64_t Elf64_Lword; > > typedef uint64_t Elf64_Xword; > > I'm not sure there is any. It's just something that OpenSolaris code > expects. I looked a bit further at this and I think that Lword probably changes it's size on OpenSolaris to be 32 bits if the code is being compiled in 32 bit mode whereas Xword is always 64 bits. -- John Birrell From owner-freebsd-arm@FreeBSD.ORG Fri Oct 6 19:30:19 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 012A816A4E7 for ; Fri, 6 Oct 2006 19:30:18 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C4FA43D53 for ; Fri, 6 Oct 2006 19:30:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k96JT7i1051636 for ; Fri, 6 Oct 2006 13:29:08 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 06 Oct 2006 13:28:17 -0600 (MDT) Message-Id: <20061006.132817.-593216915.imp@bsdimp.com> To: freebsd-arm@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 06 Oct 2006 13:29:08 -0600 (MDT) Subject: NetSilicon NS9xxx support 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: Fri, 06 Oct 2006 19:30:19 -0000 Greetings, I've recently became aware of the NetSilicon NS9xxx parts. I was wondering if anybody is working on FreeBSD support for them (or if I've overlooked support for them in the tree). They seem to have an arm9 core (ARM926EJ) and look interesting for certain market segments. Warner