From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/7] FPGA cleanup + zynq support
Date: Wed, 01 May 2013 17:35:12 +0200 [thread overview]
Message-ID: <51813630.5020808@monstr.eu> (raw)
In-Reply-To: <20130501151409.GV25397@bill-the-cat>
On 05/01/2013 05:14 PM, Tom Rini wrote:
> On Wed, May 01, 2013 at 10:59:16AM +0200, Michal Simek wrote:
>
>> Fpga code is pretty old and none has tried to clean it up.
>> My attempt is related to new code I want to push to mainline
>> which is add support for checking bitstream and if bitstream
>> is valid for the selected device.
>> For this I need to do cleanup code and move code
>> from cmd_fpga.c to fpga.c in driver folder.
>
> Aside from my comments to 4/7, everything else looks good and a step
> forward.
ok
> Looking at 7/7 however, it seems like:
> - None of CONFIG_SYS_XILINX_IF_* are used
> - CONFIG_SYS_... model definitions... aren't used, now that CONFIG_FPGA
> isn't a bitfield anymore, and are only used by configs that still act
> like it is.
>
> So we could just clean up and remove those parts of the header, yes?
yep, you are right. I will create one more patch which remove these values.
(It should be done in 2008).
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/20130501/bda9ce86/attachment.pgp>
prev parent reply other threads:[~2013-05-01 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 8:59 [U-Boot] [PATCH v2 0/7] FPGA cleanup + zynq support Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 1/7] fpga: Clean coding style Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 2/7] fpga: Fix debug message compilation error Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 3/7] cmd: fpga: Clean coding style Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 4/7] cmd: fpga: Move fpga_loadbitstream to fpga.c Michal Simek
2013-05-01 15:03 ` Tom Rini
2013-05-01 15:29 ` Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 5/7] cmd: fpga: Do not include net.h Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 6/7] fpga: zynq: Add support for loading bitstream Michal Simek
2013-05-01 8:59 ` [U-Boot] [PATCH v2 7/7] fpga: Check device name against bitstream name Michal Simek
2013-05-01 15:14 ` [U-Boot] [PATCH v2 0/7] FPGA cleanup + zynq support Tom Rini
2013-05-01 15:35 ` 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=51813630.5020808@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