From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RESEND 2/3] driver/ddr/altera/: Add the sdram calibration portion
Date: Sat, 25 Apr 2015 19:27:13 +0200 [thread overview]
Message-ID: <20150425172713.GA16666@pollux.denx.de> (raw)
In-Reply-To: <1429193516-11179-3-git-send-email-dinguyen@opensource.altera.com>
Hi!
> +++ b/drivers/ddr/altera/Makefile
> @@ -0,0 +1,12 @@
> +#
> +# (C) Copyright 2000-2003
> +# Wolfgang Denk, DENX Software Engineering, wd at denx.de.
Umm. Looks like nothing of Wolfgang's original code is remaining at this point,
you can delete this.
> +/******************************************************************************
> + ******************************************************************************
> + ** NOTE: Special Rules for Globale Variables **
> + ** **
They are global, not globale.
> + ** All global variables that are explicitly initialized (including **
> + ** explicitly initialized to zero), are only initialized once, during **
> + ** configuration time, and not again on reset. This means that they **
> + ** preserve their current contents across resets, which is needed for some **
> + ** special cases involving communication with external modules. In **
> + ** addition, this avoids paying the price to have the memory initialized, **
> + ** even for zeroed data, provided it is explicitly set to zero in the code, **
> + ** and doesn't rely on implicit initialization. **
Is this true for variables in this .c file, or for all of them?
> +/*
> + * Temporary workaround to place the initial stack pointer at a safe
> + * offset from end
> + */
> +asm(".global __alt_stack_pointer");
> +asm("__alt_stack_pointer = " __stringify(STACK_POINTER));
How is this different from normal variable?
> +/* For HPS running on actual hardware */
> +
> +#define DLEVEL 0
DEBUG_LEVEL?
> +/*
> + * space around comma is required for varargs macro to remove comma if args
> + * is empty
> + */
> +#define BFM_GBL_SET(field, value)
> +#define BFM_GBL_GET(field) ((long unsigned int)0)
> +#define BFM_STAGE(stage)
> +#define BFM_INC_VFIFO
> +#define COV(label)
I don't get the comment, or the macros. Can you just remove them?
Thanks,
Pavel
next prev parent reply other threads:[~2015-04-25 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:11 [U-Boot] [PATCH RESEND 0/3] drivers/ddr/altera: Add the DDR controller driver for SoCFPGA dinguyen at opensource.altera.com
2015-04-16 14:11 ` [U-Boot] [PATCH RESEND 1/3] driver/ddr/altera: Add DDR driver for Altera's SDRAM controller dinguyen at opensource.altera.com
2015-04-17 12:31 ` Pavel Machek
2015-04-17 15:20 ` Dinh Nguyen
2015-04-17 20:44 ` Pavel Machek
2015-04-16 14:11 ` [U-Boot] [PATCH RESEND 2/3] driver/ddr/altera/: Add the sdram calibration portion dinguyen at opensource.altera.com
2015-04-25 17:27 ` Pavel Machek [this message]
2015-04-16 14:11 ` [U-Boot] [PATCH RESEND 3/3] arm: socfpga: enable the Altera SDRAM controller driver dinguyen at opensource.altera.com
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=20150425172713.GA16666@pollux.denx.de \
--to=pavel@denx.de \
--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