From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 24 13:00:09 2008 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFE4C106567D for ; Thu, 24 Jul 2008 13:00:08 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from semihalf.com (semihalf.com [206.130.101.55]) by mx1.freebsd.org (Postfix) with ESMTP id BA7CB8FC12 for ; Thu, 24 Jul 2008 13:00:08 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by semihalf.com (8.13.1/8.13.1) with ESMTP id m6OCk8k0019020; Thu, 24 Jul 2008 06:46:09 -0600 Received: from [77.113.186.154] (apn-77-113-186-154.gprs.plus.pl [77.113.186.154]) by mail.semihalf.com (Postfix) with ESMTP id 2C21F142DD; Thu, 24 Jul 2008 14:50:28 +0200 (CEST) Message-ID: <4888798B.2050903@semihalf.com> Date: Thu, 24 Jul 2008 14:46:03 +0200 From: Rafal Jaworowski Organization: Semihalf MIME-Version: 1.0 To: "M. Warner Losh" References: <20080723.164741.163264646.imp@bsdimp.com> <20080723.213817.1661913390.imp@bsdimp.com> In-Reply-To: <20080723.213817.1661913390.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: powerpc@freebsd.org Subject: Re: Device trees X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2008 13:00:09 -0000 M. Warner Losh wrote: > In message: <106CEF8A-EA8A-48BC-BAF7-B9C112F58A92@mac.com> > Marcel Moolenaar writes: > : No, it doesn't. > > Is there any reason it doesn't? Having looked at the dtc stuff, it > seems to have all the requirements of device enumeration that we > talked about at BSDcan... At the time FreeBSD/MPC85xx was developed the flattened device tree concept was only getting momentum on Linux, so it was very much fluctuating. But the main reason was it's quite a bit of work to put everything together and it wasn't a critical item for the port. FDT is more or less what we discussed in May, and I think it was mentioned as one of the possible ways to go. Please note however the FDT infrastructure is quite heavy and getting it right needs to account for the non-code dependencies and elements too: - adopting external (GPL) tools, or providing our own - working out DTS layouts, OF bindings definitions and conventions (and their further maintenance) so that they can be used on architectures other that PowerPC (as having a modern device resources representation accross different architectures in FreeBSD was very important aspect of our discussions) Rafal