public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] xilinx FPGA code
Date: Mon, 12 Nov 2007 20:19:27 +0100	[thread overview]
Message-ID: <200711122019.27928.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <c166aa9f0711121027p579682c2xe43ecd3faa707183@mail.gmail.com>

Hi Andrew,

you are right, the FPGA code definitely needs some cleanup.

On Monday 12 November 2007 19:27:46 Andrew Dyer wrote:
> A couple of "IMHO" comments about this code in no particular order:
>
> Is there any reason to have spartan2.c, virtex2.c and spartan3.c? They
> are pretty much copies of each other with search and replace.
ack.
>
> local PRINTF should be replaced with the global 'debug' macro.
ack.
>
> this issue behind this patch should be addressed (relocating null pointers)
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/22918
I posted a couple of patches a few minutes before your posting arrived.
My 2nd patch addressed this issue (please apologize that I forgot to enumerate
them as PATCH x/5. I forgot git-format-patch's -n option and noticed that to 
late.)

> I believe the edict was given by wd@ that CFG_HZ was always to be
> 1000, and delays can be spec'd in units of ms rather than based off of
> CFG_HZ
Probably yes, but I am not sure if we might need sub-ms-timing.

>
> could do with some whitespace cleanup & reformatting to 80 cols.
There are some other coding style issues like braces for single statements.

I am willing to implement some of your/our ideas. But first I am awaiting 
my five patches to get it in :-)

Matthias

  reply	other threads:[~2007-11-12 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 18:27 [U-Boot-Users] xilinx FPGA code Andrew Dyer
2007-11-12 19:19 ` Matthias Fuchs [this message]
2007-11-13  7:15   ` [U-Boot-Users] Help Loading I.MX21 Demetris Zavorotnichenko
2007-12-03 11:04     ` Midhun A

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=200711122019.27928.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