From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754458AbdBRUxm (ORCPT <rfc822;w@1wt.eu>);
        Sat, 18 Feb 2017 15:53:42 -0500
Received: from mail-pf0-f175.google.com ([209.85.192.175]:36561 "EHLO
        mail-pf0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753833AbdBRUxk (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 18 Feb 2017 15:53:40 -0500
Date: Sat, 18 Feb 2017 12:45:09 -0800
From: Moritz Fischer <moritz.fischer@ettus.com>
To: Alan Tull <delicious.quinoa@gmail.com>
Cc: "Nadathur, Sundar" <sundar.nadathur@intel.com>,
        Yves Vandervennet <yves.vandervennet@linux.intel.com>,
        Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
        "matthew.gerlach@linux.intel.com" <matthew.gerlach@linux.intel.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        "linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>
Subject: Re: [RFC 7/8] fpga-region: add sysfs interface
Message-ID: <20170218204509.GA32544@live.com>
References: <CANk1AXTxSrtXmfO53jVx3EqmKc_KWptbpAkmkSttCdA-BXowVw@mail.gmail.com>
 <20170215180612.GB3317@obsidianresearch.com>
 <CANk1AXSTMynxMrDZ=aHsoX4naqByJnsRXPBvRGTSBpv2_5WptQ@mail.gmail.com>
 <alpine.DEB.2.20.1702151133150.2458@mgerlach-VirtualBox>
 <20170215203734.GC5531@obsidianresearch.com>
 <CAAtXAHfDXCcKutuLOWq0cK3zBp2ujV+GcvC9bYSFw==guOzBdA@mail.gmail.com>
 <alpine.DEB.2.11.1702171627290.3664@artsy.artland.art>
 <20170218023010.GA8244@live.com>
 <1CC272501B5BC543A05DB90AA509DED50AF5EC@fmsmsx122.amr.corp.intel.com>
 <CANk1AXT7EMDw-5qWqKCDJcwySQjhhVGf_1m-b9NTbyzVRkO7cg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANk1AXT7EMDw-5qWqKCDJcwySQjhhVGf_1m-b9NTbyzVRkO7cg@mail.gmail.com>
User-Agent: Mutt/1.7.0 (2016-08-17)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, Feb 18, 2017 at 02:10:43PM -0600, Alan Tull wrote:
> On Sat, Feb 18, 2017 at 6:45 AM, Nadathur, Sundar
> <sundar.nadathur@intel.com> wrote:
> 
> > Hi all,
> >    Interesting discussion. The discussion so far has brought out many concerns such as OS independence. There is an existing format, well-known to developers, with widespread support, and which is quite extensible: Type-Length-Value triples.
> >
> > To elaborate, a TLV-based format has many advantages:
> > * It is highly extensible in many ways
> >    -- You can express structures and arrays using TLVs. Our needs right now may seem limited but requirements grow over time.
> >    -- The space of Type values can be decomposed into standard pre-defined values that are in upstreamed code, and possibly experimental or feature-specific values.
> >    -- Forward compatibility: We can write parsers that can skip unexpected type values, thus allowing old parsers to work with new additions. With some tweaks, old parsers can also reject unexpected values in some ranges while accepting them in other ranges.
> > * It is OS-independent.
> > * It can be easily parsed, in kernel or user space.

Are there other users of the format? I have to admit I didn't look very
long, but couldn't find any libs / existing code at a first glance.

> > * It can be validated, in terms of Type values, acceptable lengths, etc.
> >
> > It  is not directly human-readable but that can be easily addressed with a tool that parses TLVs.
> >
> > Compared to some other proposals:
> > * Compared to DTs, TLVs are OS-independent.

That's just alternative facts here. Just because Linux uses fdt for
devicetree blobs it is *not* OS dependent. There are several (see
last email) non-Linux users of fdt / libfdt.

Thanks,

Moritz