From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Some improvements for the FPGA subsystem
Date: Wed, 14 Nov 2007 08:56:01 +0100 [thread overview]
Message-ID: <200711140856.01391.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <OF4D685D42.D849538D-ON88257392.006347E8-88257392.00644E1C@selinc.com>
Hi Bruce,
On Tuesday 13 November 2007 19:15, Bruce_Leonard at selinc.com wrote:
> >
> > Perhaps you guys can give a little ack reply to my five FPGA patches. I
> did
> > not see any no-go comment on any of them, uuh.
> >
> > Matthias
>
> Sorry, in my haste and stupidity I failed to read your entire original
> post and see that you had patches :(.
>
> ACK everything with the following question:
>
>
> - rc = fpga_load(dev, swapdata, swapsize);
> - free(swapdata);
> + rc = fpga_load(dev, dataptr, swapsize);
> return rc;
>
> I see you're using the size pulled from the BIT file rather than the size
> passed into the parameter (which IMOHO is the right way to do it), but you
> left the name of the variable as 'swapsize' which isn't really relevant
> anymore since there's no swapping going on. I don't care since I know
I put this on my list.
> what's going on, but it might be cleaner for future generations to rename
> it to something more descriptive of what it really is now. Also, on a 'I
> REALLY don't care' note, how much work do you think it would be to remove
> the requirement of having a size on the command line for this operation?
> Since the 'size' parameter is never used, I'd like to see it gone. If
> it's too much work, I can do it sometime when I'm bored ;). Just a
> thought.
You are right. You do not need to pass the size parameter to the 'fpga loadb'
command at all. Only 'fpga load' still needs it.
Matthias
prev parent reply other threads:[~2007-11-14 7:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 16:45 [U-Boot-Users] RFC: Some improvements for the FPGA subsystem Matthias Fuchs
2007-11-12 0:17 ` Grant Likely
2007-11-12 9:15 ` w.wegner at astro-kom.de
2007-11-12 9:45 ` Matthias Fuchs
2007-11-12 10:06 ` w.wegner at astro-kom.de
2007-11-12 13:24 ` Jerry Van Baren
2007-11-12 14:51 ` Matthias Fuchs
2007-11-12 15:00 ` Jerry Van Baren
2007-12-10 12:04 ` w.wegner at astro-kom.de
2007-12-11 17:00 ` Matthias Fuchs
2007-12-12 10:44 ` w.wegner at astro-kom.de
2007-12-13 9:23 ` Matthias Fuchs
2007-11-12 22:55 ` Bruce_Leonard at selinc.com
2007-11-12 23:09 ` Grant Likely
2007-11-13 8:34 ` Matthias Fuchs
2007-11-13 18:15 ` Bruce_Leonard at selinc.com
2007-11-14 7:56 ` Matthias Fuchs [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=200711140856.01391.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox