From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3 v3] iMX5: EfikaMX: Preliminary board support
Date: Wed, 19 Jan 2011 15:36:27 +0100 [thread overview]
Message-ID: <201101191536.27666.marek.vasut@gmail.com> (raw)
In-Reply-To: <20110119084941.CF9F52FC@gemini.denx.de>
On Wednesday 19 January 2011 09:49:41 Wolfgang Denk wrote:
> Dear Marek Vasut,
>
> In message <1295379040-11563-3-git-send-email-marek.vasut@gmail.com> you
wrote:
> > Supported:
> > MMC
> > IDE
> > PMIC
> > SPI flash
> > LEDs
>
> ...
>
> > +/***********************************************************************
> > ******* + * Compile-time error checking
> > +
> > ************************************************************************
> > ******/
>
> Incorrect multiline comment style.
>
> I really do not understand why you submit this again, after we
> discussed this in lenght both by e-main and on IRC.
>
> Please fix it globally, the code will not go in as is.
Mistake, sorry ... I have it fixed in my tree, just checked.
>
> > +/***********************************************************************
> > ******* + * Board identification
> > +
> > ************************************************************************
> > ******/ +static u32 board_rev;
>
> Be careful!! This way board_rev will be located in bss, and BSS data
> MUST NOT be accessed before relocation, but it appears you to this.
>
> This must be fixed.
Dang, good catch, thanks.
>
> > +int board_init(void)
> > +{
> > + gd->bd->bi_arch_number = MACH_TYPE_MX51_LANGE51;
> > + gd->bd->bi_boot_params = PHYS_SDRAM_1 + 0x100;
>
> Is this the correct MACH_TYPE for the EfikaMX board?
Apparently it is, they renamed the thing. Lange is probably a codename.
>
> > +/*
> > + * Bootloader Components Configuration
> > + */
> > +#define CONFIG_CMD_SPI
> > +#define CONFIG_CMD_SF
> > +#define CONFIG_CMD_MMC
> > +#define CONFIG_CMD_FAT
> > +#define CONFIG_CMD_IDE
> > +#undef CONFIG_CMD_IMLS
>
> PLease be consistent - either always use space after #define
> (recommended), or always use TAB, but do not mix both styles.
>
> > +/*
> > + * ATAG setup
> > + */
> > +#define CONFIG_CMDLINE_TAG 1 /* enable passing of ATAGs */
> > +#define CONFIG_REVISION_TAG 1
> > +#define CONFIG_SETUP_MEMORY_TAGS 1
> > +#define CONFIG_INITRD_TAG 1
>
> Please omit all these '1'. Please fix globally...
>
> > +#define CONFIG_HARD_SPI 1
> > +#define CONFIG_MXC_SPI 1
>
> ... i.e. here and in similar places, too.
Fixed in v4, thanks for the review
>
>
> Best regards,
>
> Wolfgang Denk
next prev parent reply other threads:[~2011-01-19 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 19:30 [U-Boot] [PATCH 1/3] MC13892: Add SWx buck switchers definitions Marek Vasut
2011-01-18 19:30 ` [U-Boot] [PATCH 2/3] MX51EVK: Use SWx macros in PMIC init Marek Vasut
2011-01-19 9:12 ` Stefano Babic
2011-01-19 10:46 ` Sergei Shtylyov
2011-01-18 19:30 ` [U-Boot] [PATCH 3/3 v3] iMX5: EfikaMX: Preliminary board support Marek Vasut
2011-01-19 8:49 ` Wolfgang Denk
2011-01-19 14:36 ` Marek Vasut [this message]
2011-01-18 20:57 ` [U-Boot] [PATCH 1/3] MC13892: Add SWx buck switchers definitions Jason Liu
2011-01-19 9:11 ` 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=201101191536.27666.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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