From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Mon, 31 Mar 2008 13:13:33 +0200
Subject: [U-Boot-Users] ppc4xx: gpio setup broken for ppc405ep
In-Reply-To: <6a6049b80803310351v751b21f4ya120841fb7a5845f@mail.gmail.com>
References: <6a6049b80803271104x598b47adta1dc97f9d13102c@mail.gmail.com>
	<200803311120.05937.sr@denx.de>
	<6a6049b80803310351v751b21f4ya120841fb7a5845f@mail.gmail.com>
Message-ID: <200803311313.33224.sr@denx.de>
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

On Monday 31 March 2008, M B wrote:
> >  No. High and low *are* swapped. I just re-checked with users manual rev
> > 1.08. GPIO0_OSRH has offset 0x0C and GPIO0_OSRL has offset 0x08. So this
> > matches the offsets of all other 4xx GPIO registers I have seen so far.
>
> You're right. This was fixed in v 1.06, so this explains why I and
> ppc405.h was wrong.
> btw. v1.10 of the Users Manual is out.

Thanks. I'll download right away.

> >  I'm not really sure if this is true though since  Taihu is using
> >  gpio_set_chip_configuration() without known problems. Could you please
> >  re-check with AMCC support, if this statement for 405EP is correct? If
> > this pin assignment of the 405EP GPIO block is incompatible with other
> > GPIO cores, like the one on 440EP or 405EX.
>
> I will do.
> All ppc405 which used the CFG_GPIO0_*{H,L} defines in their config
> file were using the "wrong" address.

No. 405EX & 405EZ which were added recently are using the correct addresses.

Best regards,
Stefan

=====================================================================
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
=====================================================================