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 S1752454AbdBOVVA (ORCPT <rfc822;w@1wt.eu>);
        Wed, 15 Feb 2017 16:21:00 -0500
Received: from mail-out.m-online.net ([212.18.0.9]:38332 "EHLO
        mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751430AbdBOVU6 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 15 Feb 2017 16:20:58 -0500
X-Auth-Info: Fuyl7ZyTKEwVQFAwVCLRJsXVMQgBkgQRmJDMWN5ZvQY=
Date: Wed, 15 Feb 2017 22:20:53 +0100
From: Anatolij Gustschin <agust@denx.de>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Alan Tull <delicious.quinoa@gmail.com>,
        Moritz Fischer <moritz.fischer@ettus.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        linux-fpga@vger.kernel.org
Subject: Re: [RFC 7/8] fpga-region: add sysfs interface
Message-ID: <20170215222053.725145a5@crub>
In-Reply-To: <20170215180612.GB3317@obsidianresearch.com>
References: <1487175261-7051-1-git-send-email-atull@kernel.org>
        <1487175261-7051-8-git-send-email-atull@kernel.org>
        <20170215172157.GA3317@obsidianresearch.com>
        <CANk1AXTxSrtXmfO53jVx3EqmKc_KWptbpAkmkSttCdA-BXowVw@mail.gmail.com>
        <20170215180612.GB3317@obsidianresearch.com>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Jason,

On Wed, 15 Feb 2017 11:06:12 -0700
Jason Gunthorpe jgunthorpe@obsidianresearch.com wrote:
...
>The kernel could detect the bitfile starts with 'Linux_FPGA_BIT/1.0\n'
>and then proceed to decode the header providing compat with the
>current scheme.
>
>This is usually the sort of stuff I'd punt to userspace, but since the
>kernel is doing request_firmware it is hard to see how that is an
>option in this case...

Interesting. We have a requirement that the complete history of FPGA
configurations (basic configuration and the sequence of following
partial reconfigurations) should be readable from FPGA manager
framework on request. Each bitfile is associated with meta-data
and one should be able to read this meta-data back for complete
reconfiguration chain. When the kernel decodes a header, it could
optionally store the data and allow to read it back on request.

Thanks,
Anatolij