Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754818Ab1BGV3K (ORCPT ); Mon, 7 Feb 2011 16:29:10 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:50880 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752388Ab1BGV3I (ORCPT ); Mon, 7 Feb 2011 16:29:08 -0500 MIME-Version: 1.0 In-Reply-To: <20110207084613.GC2723@matterhorn.lan> References: <20110207084613.GC2723@matterhorn.lan> From: Grant Likely Date: Mon, 7 Feb 2011 14:28:47 -0700 X-Google-Sender-Auth: 8Ql9f-7PzV302Vo6GODIF-0c7nk Message-ID: Subject: Re: Device Tree on ARM status report To: Grant Likely , devicetree-discuss , linaro-dev , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1042 Lines: 24 On Mon, Feb 7, 2011 at 1:46 AM, Amit Kucheria wrote: > On 11 Feb 05, Grant Likely wrote: >> 2 - Task status >> --------------- >> Core infrastructure: >> [glikely] basic infrastructure to enable dt: DONE >> [r-herring] Allow dtb to be located anywhere in RAM: DONE >> [bones] Debug dtb corruption during init: INPROGRESS >> [glikely] OF clock bindings: INPROGRESS > > Does this include the common clock framework that Jeremy had been working on? > I see no mention of that explicitly, hence the question. No, since the common clk patches are taking some time to get right, the device tree clock bindings have been decoupled from the common clk patches so that dt support doesn't get held up. When common clk gets merged, the dt support will be modified to use it. g. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/