From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5] ARM: mx31: Print the silicon version
Date: Wed, 27 Apr 2011 11:40:38 +0200 [thread overview]
Message-ID: <4DB7E496.4070400@denx.de> (raw)
In-Reply-To: <m2r58ocb39.fsf@ohwell.denx.de>
On 04/27/2011 11:11 AM, Detlev Zundel wrote:
>>>> This is due to the usage of the const in the mx3_cpu_type:
>>
>> struct mx3_cpu_type {
>> u8 srev;
>> const char *v;
>>
>> Do you agree if I drop myself the const attribute on u-boot-imx before
>> pulling your patch to the arm tree ?
>
> Sorry to jump in late,
.. not so late, we can change it...
>but why not change get_cpu_rev to 'const char *'
> which it actually is?
This is correct. However, I have not noted before that the last
introduced get_cpu_rev() in MX31 is an exception in u-boot. For all
other processors, it returns a u32 and it is defined as u32
get_cpu_rev(void).
Fabio's patch introduces a variant, because it is defined as const char
*get_cpu_rev(void). I propose to change its name (get_cpu_rev_string ?)
and add the static attribute, to make clear it is different as the
get_cpu_rev() already implemented in u-boot.
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-04-27 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 2:18 [U-Boot] [PATCH v5] ARM: mx31: Print the silicon version Fabio Estevam
2011-04-14 11:14 ` Albert ARIBAUD
2011-04-14 20:53 ` stefano babic
2011-04-15 18:07 ` Stefano Babic
2011-04-21 16:01 ` Stefano Babic
2011-04-27 9:11 ` Detlev Zundel
2011-04-27 9:40 ` Stefano Babic [this message]
2011-04-27 13:16 ` Fabio Estevam
2011-04-27 14:00 ` Stefano Babic
2011-04-27 14:57 ` Detlev Zundel
2011-04-27 16:01 ` 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=4DB7E496.4070400@denx.de \
--to=sbabic@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