From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP DIE_ID
Date: Fri, 14 Aug 2009 19:04:10 +0200 [thread overview]
Message-ID: <4A85990A.4010301@googlemail.com> (raw)
In-Reply-To: <f67028d40908140724u7076eed0m82f29c0be06a4319@mail.gmail.com>
Frederik Kriewitz wrote:
> I'm a bit confused about the u-boot code which reads the OMAP die id.
>
>>From the OMAP TRM:
> CONTROL.CONTROL_DIE_ID[127:0]
> Address: 0x4830A218
> Size: 128
>
> u-boot code: http://gitorious.org/u-boot-omap3/mainline/blobs/master/cpu/arm_cortexa8/omap3/sys_info.c#line44
>
> result: Die ID #: 04ba0054 00000020 0401463b 0401c214
> Memory Dump: 4830a218: 0401c214 0401463b 00000020 04ba0054
>
> Shouldn't u-boot read/show the die id the other way around (just as in
> the memory dump)?
>
> Please just tell me that I'm wrong :)
I wouldn't talk about right or wrong here ;) Most probably this is
just personal taste.
First, short summary about what we are talking:
u32 die_id_0; /* 0x18 */
u32 die_id_1; /* 0x1C */
u32 die_id_2; /* 0x20 */
u32 die_id_3; /* 0x24 */
id[3] = readl(&id_base->die_id_0);
id[2] = readl(&id_base->die_id_1);
id[1] = readl(&id_base->die_id_2);
id[0] = readl(&id_base->die_id_3);
sprintf(die_id, "%08x%08x%08x%08x", id[0], id[1], id[2], id[3]);
From memory dump point of view, using above example, this is
4830a218: 0401c214 CONTROL_DIE_ID[31:0]
4830a21C: 0401463b CONTROL_DIE_ID[63:32]
4830a220: 00000020 CONTROL_DIE_ID[95:64]
4830a224: 04ba0054 CONTROL_DIE_ID[127:96]
So we are printing
Die ID #: DIE_ID[127:96] DIE_ID[95:64] DIE_ID[63:32] DIE_ID[31:0]
as a 128 bit value with lowest value right and highest value left.
Is this correct?
At least, this is what I think was intended ;)
Best regards
Dirk
next prev parent reply other threads:[~2009-08-14 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 14:24 [U-Boot] OMAP DIE_ID Frederik Kriewitz
2009-08-14 17:04 ` Dirk Behme [this message]
2009-08-15 14:35 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-15 15:02 ` Frederik Kriewitz
2009-08-15 16:12 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-15 18:29 ` Frederik Kriewitz
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=4A85990A.4010301@googlemail.com \
--to=dirk.behme@googlemail.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