From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 1/3] Initial support for Marvell Orion5x SoC
Date: Wed, 13 Jan 2010 08:49:09 +0100 [thread overview]
Message-ID: <4B4D7AF5.30906@free.fr> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E2030816251F@SC-VEXCH1.marvell.com>
Prafulla Wadaskar a ?crit :
>> cpu/arm926ejs/orion5x/cpu.c | 258
> ....snip....
>
>> +int print_cpuinfo(void)
> The above checks should be #ifdefed with CONFIG_88FXXXX (SOC type)
> There is no need to check for all SoC names, this will also reduce code size.
As stated in my answer re: the declaration of the dev/rev constants, I
believe that this place, of all place, should not be conditionally built
depending on the device, because it is there to positively identify the
device/revision we're running our code on even if not built for the
right variant.
Amicalement,
--
Albert.
prev parent reply other threads:[~2010-01-13 7:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 16:03 [U-Boot] [PATCH V4 1/3] Initial support for Marvell Orion5x SoC Albert Aribaud
2010-01-10 16:03 ` [U-Boot] [PATCH V4 2/3] Add Orion5x support to 16550 device driver Albert Aribaud
2010-01-10 16:03 ` [U-Boot] [PATCH V4 3/3] Add support for the LaCie ED Mini V2 board Albert Aribaud
2010-01-11 11:56 ` Prafulla Wadaskar
2010-01-11 12:12 ` Albert ARIBAUD
2010-01-11 14:10 ` Prafulla Wadaskar
2010-01-11 17:26 ` Albert ARIBAUD
2010-01-13 12:37 ` Albert ARIBAUD
2010-01-13 14:04 ` Prafulla Wadaskar
2010-01-13 17:17 ` Albert ARIBAUD
2010-01-12 0:08 ` Tom
2010-01-10 16:42 ` [U-Boot] [PATCH V4 1/3] Initial support for Marvell Orion5x SoC Albert ARIBAUD
2010-01-11 11:22 ` Prafulla Wadaskar
2010-01-13 7:21 ` Albert ARIBAUD
2010-01-11 11:29 ` Prafulla Wadaskar
2010-01-13 7:49 ` Albert ARIBAUD [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=4B4D7AF5.30906@free.fr \
--to=albert.aribaud@free.fr \
--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