From owner-freebsd-arm@FreeBSD.ORG Thu May 11 21:35:36 2006 Return-Path: X-Original-To: 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 4078F16A551; Thu, 11 May 2006 21:35:36 +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 CA88444634; Thu, 11 May 2006 21:35:35 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4BLYv7l049582; Thu, 11 May 2006 15:34:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 11 May 2006 17:35:04 -0400 (EDT) Message-Id: <20060511.173504.81571123.imp@bsdimp.com> To: arm@freebsd.org, small@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: FreeBSD/arm evangelist 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: Thu, 11 May 2006 21:35:36 -0000 I'm looking for someone to help me out with FreeBSD/arm evangelizing. I'd like to find someone that can help me to get the word out about FreeBSD/arm. It now runs well on a number of different evaluation boards. I'd like to start a push to get the vendors of these boards to include a link on their web pages to our site, creating web pages on our site with mini-howtos, etc. If anyone would like to contribte to the project, has some time and energy and good organizational skills, please contact me. I'd hoped to perform these functions, but I'm finding that I'm not getting them done. Warner From owner-freebsd-arm@FreeBSD.ORG Fri May 12 03:32:36 2006 Return-Path: X-Original-To: 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 B9F8C16A425 for ; Fri, 12 May 2006 03:32:36 +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 A620143DAE for ; Fri, 12 May 2006 03:32:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4C3TsTV054086 for ; Thu, 11 May 2006 21:29:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 11 May 2006 23:30:03 -0400 (EDT) Message-Id: <20060511.233003.87762623.imp@bsdimp.com> To: arm@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: time_t 64 bits? 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, 12 May 2006 03:32:37 -0000 John Baldwin just asked me why time_t is 32 bits on arm. Is there any reason for it? Can we change it to 64 bits? Would this cause problems for our users? Warner From owner-freebsd-arm@FreeBSD.ORG Fri May 12 11:00:29 2006 Return-Path: X-Original-To: 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 C083016A402 for ; Fri, 12 May 2006 11:00:29 +0000 (UTC) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (cognet.ci0.org [80.65.224.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF89343D46 for ; Fri, 12 May 2006 11:00:27 +0000 (GMT) (envelope-from mlfbsd@dong.ci0.org) Received: from dong.ci0.org (localhost.ci0.org [127.0.0.1]) by dong.ci0.org (8.13.6/8.13.4) with ESMTP id k4CBbgli064429; Fri, 12 May 2006 13:37:43 +0200 (CEST) (envelope-from mlfbsd@dong.ci0.org) Received: (from mlfbsd@localhost) by dong.ci0.org (8.13.6/8.13.4/Submit) id k4CBbgQO064428; Fri, 12 May 2006 13:37:42 +0200 (CEST) (envelope-from mlfbsd) Date: Fri, 12 May 2006 13:37:42 +0200 From: Olivier Houchard To: "M. Warner Losh" Message-ID: <20060512113742.GA64377@ci0.org> References: <20060511.233003.87762623.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060511.233003.87762623.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Cc: arm@freebsd.org Subject: Re: time_t 64 bits? 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, 12 May 2006 11:00:29 -0000 On Thu, May 11, 2006 at 11:30:03PM -0400, M. Warner Losh wrote: > John Baldwin just asked me why time_t is 32 bits on arm. Is there any > reason for it? Can we change it to 64 bits? Would this cause > problems for our users? > > Warner Well it's 32 bits because it's 32 bits on i386 too. But I guess if such a change has to be done, now is a good time to do so, not sure if it can have a negative impact on performances. Olivier From owner-freebsd-arm@FreeBSD.ORG Fri May 12 14:38:53 2006 Return-Path: X-Original-To: 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 08D0A16A4CA for ; Fri, 12 May 2006 14:38:53 +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 81D8C43D48 for ; Fri, 12 May 2006 14:38:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4CEb2On066256; Fri, 12 May 2006 08:37:03 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 12 May 2006 10:37:12 -0400 (EDT) Message-Id: <20060512.103712.54187514.imp@bsdimp.com> To: mlfbsd@ci0.org From: "M. Warner Losh" In-Reply-To: <20060512113742.GA64377@ci0.org> References: <20060511.233003.87762623.imp@bsdimp.com> <20060512113742.GA64377@ci0.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arm@freebsd.org Subject: Re: time_t 64 bits? 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, 12 May 2006 14:38:56 -0000 In message: <20060512113742.GA64377@ci0.org> Olivier Houchard writes: : On Thu, May 11, 2006 at 11:30:03PM -0400, M. Warner Losh wrote: : > John Baldwin just asked me why time_t is 32 bits on arm. Is there any : > reason for it? Can we change it to 64 bits? Would this cause : > problems for our users? : > : > Warner : : Well it's 32 bits because it's 32 bits on i386 too. But I guess if such a : change has to be done, now is a good time to do so, not sure if it can have : a negative impact on performances. ironically, time_t isn't used in time critical applications. Sounds like we should try it and see if there are any negative implications to it... Warner