From: Moritz Fischer <moritz.fischer@ettus.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] common: image: update boot_get_fpga to support arbitrary fpga image
Date: Mon, 20 Feb 2017 09:35:08 -0800 [thread overview]
Message-ID: <CAAtXAHc72HMwHnAypyhMppt8HOMBPwazkDGOSnu0OfP6sYZjYA@mail.gmail.com> (raw)
In-Reply-To: <908d922a-3b53-3477-9489-cc1a5cfc27ae@xilinx.com>
Hi all,
On Mon, Feb 20, 2017 at 6:59 AM, Michal Simek <michal.simek@xilinx.com> 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, ...).
We're trying to come up with an extensible format that would allow us
to add stuff like
encryption keys etc.
Cheers,
Moritz
[1] https://patchwork.kernel.org/patch/9574399/
next prev parent reply other threads:[~2017-02-20 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 19:49 [U-Boot] [PATCH 0/2] common: fitimage support for arbitrary fpga type Dalon Westergreen
2017-02-19 19:49 ` [U-Boot] [PATCH 1/2] common: image: update boot_get_fpga to support arbitrary fpga image Dalon Westergreen
2017-02-19 20:07 ` Marek Vasut
2017-02-19 20:43 ` Dalon Westergreen
2017-02-19 20:49 ` Marek Vasut
2017-02-19 20:58 ` Dalon Westergreen
2017-02-19 21:12 ` Marek Vasut
2017-02-19 21:21 ` Dalon Westergreen
2017-02-19 21:26 ` Marek Vasut
2017-02-20 9:24 ` Michal Simek
2017-02-20 14:24 ` Dalon Westergreen
2017-02-20 9:22 ` Michal Simek
2017-02-20 14:30 ` Dalon Westergreen
2017-02-20 14:59 ` Michal Simek
2017-02-20 17:35 ` Moritz Fischer [this message]
2017-02-20 22:38 ` Marek Vasut
2017-02-19 19:49 ` [U-Boot] [PATCH 2/2] common: bootm: add support for arbitrary fgpa configuration Dalon Westergreen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAtXAHc72HMwHnAypyhMppt8HOMBPwazkDGOSnu0OfP6sYZjYA@mail.gmail.com \
--to=moritz.fischer@ettus.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.