From: txcotrader <txcotrader@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC4XX Custom Board - Failing to read I2C
Date: Thu, 4 Apr 2013 10:43:03 -0700 (PDT) [thread overview]
Message-ID: <1365097383623-151561.post@n7.nabble.com> (raw)
In-Reply-To: <1365016197420-151444.post@n7.nabble.com>
I feel like something "different" is happening when executing the io.h->out_8
function. Could somebody help me understand this op code
v2013.01.01 Code:
extern inline void out_8(volatile unsigned char __iomem *addr, u8 val)
{
__asm__ __volatile__("sync;\n"
"stb%U0%X0 %1,%0;\n"
: "=m" (*addr)
: "r" (val));
}
Old 1.7.02 Code:
extern inline void out_8(volatile unsigned char __iomem *addr, int val)
{
__asm__ __volatile__("stb%U0%X0 %1,%0; eieio" : "=m" (*addr) : "r"
(val));
}
So I understand the sync op code but what is going on here? Could someone
with some expertise explain "stb%U0%X0 %1,%0" and "stb%U0%X0 %1,%0; eieio".
Thanks!
--
View this message in context: http://u-boot.10912.n7.nabble.com/PPC4XX-Custom-Board-Failing-to-read-I2C-tp151298p151561.html
Sent from the U-Boot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-04-04 17:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:48 [U-Boot] PPC4XX Custom Board - Failing to read I2C txcotrader
2013-04-03 0:51 ` Stefan Roese
2013-04-03 16:15 ` txcotrader
2013-04-03 17:08 ` Stefan Roese
2013-04-03 17:29 ` txcotrader
2013-04-03 17:54 ` Anatolij Gustschin
2013-04-03 19:09 ` txcotrader
2013-04-04 17:43 ` txcotrader [this message]
2013-04-04 22:18 ` Rommel Custodio
2013-04-04 22:26 ` txcotrader
2013-04-05 0:04 ` txcotrader
2013-04-05 6:04 ` Stefan Roese
2013-04-08 12:26 ` txcotrader
2013-04-08 13:33 ` Stefan Roese
2013-04-08 14:16 ` txcotrader
2013-04-08 14:34 ` Stefan Roese
2013-04-08 19:54 ` txcotrader
2013-04-09 15:49 ` Stefan Roese
2013-07-24 22:58 ` txcotrader
2013-07-25 4:33 ` Stefan Roese
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=1365097383623-151561.post@n7.nabble.com \
--to=txcotrader@gmail.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