From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Exynos 5800/5422 CPU ID inconsistency.
Date: Wed, 26 Aug 2015 15:09:58 +0200 [thread overview]
Message-ID: <55DDBAA6.6080307@samsung.com> (raw)
Hello,
The s5p_cpu_id variable is set in here:
arch/arm/mach-exynos/include/mach/cpu.h
For value 0x422, found in pro id register, the s5p_cpu_id is set as
0x5800. I think, that hiding the real info is wrong and misleading.
I don't have documentation for E5800, but maybe there is some additional
register like package id to recognise the SoC variant.
I'm pointing this issue, because for older boards, we used this
information to set the $fdtfile environment variable name, to next load
proper fdt from partition before boot the kernel.
Now, I would like use the s5p_cpu_id to set the fdtfile name for Odroid
XU3/4, but the value is bad.
I would like fix this value to the real one, but then, the CPU name will
change on Chromebooks.
To fix this we could add "cpu-name" property to device tree, and then
print it.
What do you think about this?
Best regards,
--
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com
next reply other threads:[~2015-08-26 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 13:09 Przemyslaw Marczak [this message]
2015-08-26 13:37 ` [U-Boot] Exynos 5800/5422 CPU ID inconsistency Simon Glass
2015-08-26 20:56 ` Sjoerd Simons
2015-08-27 10:23 ` Przemyslaw Marczak
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=55DDBAA6.6080307@samsung.com \
--to=p.marczak@samsung.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