From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 6/6] fpga: xilinx: Simplify load/dump/info function handling
Date: Mon, 17 Mar 2014 07:27:08 +0100 [thread overview]
Message-ID: <532695BC.2070204@monstr.eu> (raw)
In-Reply-To: <20140314202707.GT16360@bill-the-cat>
On 03/14/2014 09:27 PM, Tom Rini wrote:
> On Thu, Mar 13, 2014 at 03:52:48PM +0100, Michal Simek wrote:
>
>> Connect FPGA version with appropriate operations
>> to remove huge switch-cases for every FPGA family.
>> Tested on Zynq. Spartan2/Spartan3/Virtex2 just compile test.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>
> I like the concept. Did you go through the u-boot.map files on
> spartan/etc to make sure we aren't discarding things now? That'd be the
> follow up on compile testing the series.
Good that you like the concept - this was my intention for this RFC.
I will check it that's not a problem. Enough time to finish this
for the next release.
The next patch I want to do in fpga is to synchronize load/loadbitstream
commands.
The reason is that we need to add one more load which is
currently called loadfs which takes bitstream from filesystem
and load it with small chunks which are passed to programmable IP.
The whole reason is that system is working with limited amount
of memory that's why can't be done in 2 steps that fatload is called
and move bitstream to memory and then fpga load setup one DMA
to program it.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140317/33599c06/attachment.pgp>
prev parent reply other threads:[~2014-03-17 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:52 [U-Boot] [RFC PATCH 1/6] fpga: spartan2: Avoid CamelCase Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 2/6] fpga: spartan3: " Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 3/6] fpga: virtex2: " Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 4/6] fpga: xilinx: Avoid CamelCase for in Xilinx_desc Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 5/6] fpga: xilinx: Fix the rest of CamelCases Michal Simek
2014-03-13 14:52 ` [U-Boot] [RFC PATCH 6/6] fpga: xilinx: Simplify load/dump/info function handling Michal Simek
2014-03-14 20:27 ` Tom Rini
2014-03-17 6:27 ` Michal Simek [this message]
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=532695BC.2070204@monstr.eu \
--to=monstr@monstr.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox