All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: Add titanium board support (i.MX6 based)
Date: Thu, 11 Apr 2013 18:39:05 +0200	[thread overview]
Message-ID: <5166E729.2090403@denx.de> (raw)
In-Reply-To: <CAOMZO5A5DoaXCLqLr0tRdxew8r5V1N4OPNZ1Gf39wY1nLbJDhA@mail.gmail.com>

Hi Fabio,

On 11.04.2013 17:48, Fabio Estevam wrote:
>> +u32 get_board_rev(void)
>> +{
>> +       return get_cpu_rev();
>> +}
> 
> You can drop this, since I recently sent a patch that places it on a
> common location.

Hmmm, removing this function results in this error:

$ ./MAKEALL titanium
Configuring for titanium - Board: titanium, Options: IMX_CONFIG=board/freescale/titanium/imximage.cfg
make: *** [u-boot] Error 139
arm-linux-gnueabi-size: ./u-boot: File format not recognized
arch/arm/lib/libarm.o: In function `setup_revision_tag':
/home/stefan/git/u-boot/u-boot/arch/arm/lib/bootm.c:215: undefined reference to `get_board_rev'
...

So your patch is not in mainline yet? Is it in the ARM
custodian repo? Then the pending ARM PR will solve this.
 
>> +/* Physical Memory Map */
>> +#define CONFIG_NR_DRAM_BANKS           1
>> +#define PHYS_SDRAM                     MMDC0_ARB_BASE_ADDR
>> +#define PHYS_SDRAM_SIZE                        (1u * 512 * 1024 * 1024)
> 
> When I initially submitted the Wandboard support patch, Wolfgang
> commented that this '1u' is not really needed, and then I used
> SZ_512M, which provides better readability. Maybe you can do the same
> here?

I have no strong feelings here, but with Wolfgang preference of the
"<<" notation, I'll change to this:

#define PHYS_SDRAM_SIZE		(512 << 20)

I find this also quite easy to read: "x << 10" is "x KiB" and
"y << 20" is "y MiB". Nothing obscured via some defines.

Best regards,
Stefan

  reply	other threads:[~2013-04-11 16:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  7:17 [U-Boot] [PATCH] imx: Add titanium board support (i.MX6 based) Stefan Roese
2013-04-10  7:52 ` Heiko Schocher
2013-04-10 12:05 ` Wolfgang Denk
2013-04-10 12:13 ` Wolfgang Denk
2013-04-11  8:00   ` Stefan Roese
2013-04-11  3:36 ` Fabio Estevam
2013-04-11  5:41   ` Wolfgang Denk
2013-04-11  9:04 ` [U-Boot] [PATCH v2] " Stefan Roese
2013-04-16  7:19   ` [U-Boot] [PATCH v3] " Stefan Roese
2013-04-16  7:50     ` Stefano Babic
2013-04-16 12:05       ` Stefan Roese
2013-04-16 12:55   ` [U-Boot] [PATCH v4] " Stefan Roese
2013-04-17  8:22     ` Stefano Babic
2013-04-17  8:27   ` [U-Boot] [PATCH 4 (resend)] " Stefan Roese
2013-04-17 10:15     ` Wolfgang Denk
2013-04-17 10:27       ` Stefan Roese
2013-04-17 10:32   ` [U-Boot] [PATCH v5] " Stefan Roese
2013-04-11 15:48 ` [U-Boot] [PATCH] " Fabio Estevam
2013-04-11 16:39   ` Stefan Roese [this message]
2013-04-11 16:54     ` Fabio Estevam
2013-04-22  8:07 ` Stefano Babic
2013-04-22  8:12   ` Stefan Roese
2013-04-22  8:33     ` Stefano Babic

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=5166E729.2090403@denx.de \
    --to=sr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.