From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Mon, 20 Feb 2017 23:38:01 +0100 Subject: [U-Boot] [PATCH 1/2] common: image: update boot_get_fpga to support arbitrary fpga image In-Reply-To: References: <1487533799-28788-1-git-send-email-dwesterg@gmail.com> <1487533799-28788-2-git-send-email-dwesterg@gmail.com> <78c71e1d-999a-d9da-0326-c34e7caae3d3@denx.de> <1487537033.13957.12.camel@gmail.com> <1487537924.13957.20.camel@gmail.com> <7ed755d4-7ae0-d1c6-aeeb-8c463e6845c1@xilinx.com> <1487601019.6111.35.camel@gmail.com> <908d922a-3b53-3477-9489-cc1a5cfc27ae@xilinx.com> Message-ID: <0adfe6e1-e365-faa8-4fa7-8cf674374595@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 02/20/2017 06:35 PM, Moritz Fischer wrote: > Hi all, > > On Mon, Feb 20, 2017 at 6:59 AM, Michal Simek wrote: > >> Definitely I am open to improve this subsystem to make it more flexible. > > Over at linux-fpga ([1]) we're currently discussing the idea of coming > up with a header > format (vendor neutral) that we stitch onto the fpga image to allow the fpga-mgr > to derive certain features of the image from the image itself (i.e. is > the image encrypted, > compressed, ...). Can you CC me on that discussion ? I think it'd be for the best to use DT for the header format, it's documented and vendor-neutral already. > We're trying to come up with an extensible format that would allow us > to add stuff like > encryption keys etc. Nothing like a NIH format :) > Cheers, > > Moritz > > > [1] https://patchwork.kernel.org/patch/9574399/ > -- Best regards, Marek Vasut