From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [pull] tilcdc-next for 3.9 Date: Mon, 18 Feb 2013 14:40:12 +0200 Message-ID: <5122212C.4070808@iki.fi> References: <5121EE31.7020807@iki.fi> <51221F66.70702@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) by gabe.freedesktop.org (Postfix) with ESMTP id 92156E6265 for ; Mon, 18 Feb 2013 04:40:16 -0800 (PST) Received: by mail-la0-f45.google.com with SMTP id er20so5468556lab.32 for ; Mon, 18 Feb 2013 04:40:15 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Rob Clark Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On 2013-02-18 14:35, Rob Clark wrote: > On Mon, Feb 18, 2013 at 7:32 AM, Tomi Valkeinen wrote: >> On 2013-02-18 14:26, Rob Clark wrote: >> >>> So I'm not going to get too hung up on supporting current DT bindings >>> in the future when we have something better. But I needed something >> >> I may be mistaken, but my understanding is that DT bindings are like >> kernel's userspace APIs. After they have been merged, they have to work >> in the future kernels also. > > and that probably *eventually* makes sense when dts files are kicked > out of the kernel. For now, it doesn't really seem useful, unlike > maintaining compatibility for userspace ABI's. Why does that matter? Afaik, the dts files are in the kernel for convenience, and as examples. You can as well have the DT data in your bootloader. Or has there been a clear decision that while the dts files are in the kernel, they are considered unstable? Tomi