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 18:01:33 +0200 [thread overview]
Message-ID: <4DB83DDD.10809@denx.de> (raw)
In-Reply-To: <m2r58n91yn.fsf@ohwell.denx.de>
On 04/27/2011 04:57 PM, Detlev Zundel wrote:
> I see. Can't we consolidate all those functions into more general
> functions higher up in the specialization graph?
As I can see, the get_cpu_rev() is already a generalized function, used
in more processors. IMHO we should switch back to the usual prototype
u32 get_cpu_rev(), and print_cpuinfo() should transform the revision
number in a human readable way.
> I.e. why have static
> non-conforming functions when we could have one generic function to
> handle all users?
Yes, agree. Really I have not seen that get_cpu_rev() changed returning
a string, instead of u32 as usual. This must be fixed.
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
=====================================================================
prev parent reply other threads:[~2011-04-27 16:01 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
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 [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=4DB83DDD.10809@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 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.