From: txcotrader <txcotrader@gmail.com>
Date: Thu, 4 Apr 2013 10:43:03 -0700 (PDT)
Subject: [U-Boot] PPC4XX Custom Board - Failing to read I2C
In-Reply-To: <1365016197420-151444.post@n7.nabble.com>
References: <1364939304023-151298.post@n7.nabble.com>
	<515B7D21.6040607@denx.de>
	<1365005723957-151427.post@n7.nabble.com>
	<515C6204.9020508@denx.de>
	<1365010140176-151435.post@n7.nabble.com>
	<20130403195407.508d7df6@crub>
	<1365016197420-151444.post@n7.nabble.com>
Message-ID: <1365097383623-151561.post@n7.nabble.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.