From owner-cvs-doc@FreeBSD.ORG Fri May 12 15:29:26 2006 Return-Path: X-Original-To: cvs-doc@FreeBSD.org Delivered-To: cvs-doc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EC3D16A5A2; Fri, 12 May 2006 15:29:26 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8152143D49; Fri, 12 May 2006 15:29:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4CFT9kM016539; Fri, 12 May 2006 09:29:15 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4464A9BF.5080900@samsco.org> Date: Fri, 12 May 2006 09:29:03 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200605111952.57682.jhb@freebsd.org> <20060512.001308.126925417.imp@bsdimp.com> <44641993.5090403@samsco.org> <20060512.104954.118629167.imp@bsdimp.com> In-Reply-To: <20060512.104954.118629167.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: bmah@FreeBSD.org, andre@FreeBSD.org, cvs-doc@FreeBSD.org, jhb@FreeBSD.org, cvs-all@FreeBSD.org, doc-committers@FreeBSD.org Subject: Re: FreeBSD/arm X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2006 15:29:32 -0000 M. Warner Losh wrote: > If this is a long way of saying 'we should list it on the main page,' > I agree. :-) > I kinda wish that the marketting group had picked up on my message to them about this several months ago. But yes, there should be mention on it on the front page, and there should be at subsection of the website that describes and documents it. > One thing that the project will need to define in the coming months is > what to do about embedded architectures. ARM is approaching Tier 1 > status for an embedded system as work progresses. Others will no > doubt one day follow. > I hinted in the grandparent email that the support model for ARM, and presumably other embedded architectures, is necessairly different. Since there is no universal platform, it's hard to provide development, test, package building, QA, and security reference systems to the project. Thus, the concept of tiers that we've applied thus far doesn't really fit. I know that there has been discussion about having a tiered tier system, but I think that that doesn't really answer the underlying questions, and only ads more confusion. If you say that ARM is "embedded tier-1", what does that mean for developers who work in the MI/MD intersections of the system? Also, what does that phrase mean to the end users? Does it mean that only a small selection of AT91 systems are Tier-1, does it mean that the ARM9 ISA is Tier-1, etc? I do prefer to describe ARM support as a framework, and not in terms of the guarantees of service that 'tiers' are supposed to represent. Scott