PPC440EPx on Sequoia: /proc/iomem acts weird

Steven A. Falco sfalco at harris.com
Tue Nov 13 06:25:29 EST 2007

First I will say that I don't understand resources well enough to 
suggest a fix.  But I have done a little poking around.  In file 
arch/powerpc/platforms/44x/ppc4xx-nand.c I see one "struct resource", 
which is referenced by two "struct platform_device" items (ndfc_dev and 

In routine ppc4xx_setup_nand_node() we have two calls to 


If I comment out the second one, then there is no loop in the resource 
tree, and I can cat /proc/iomem just fine.  If both calls are present, 
then cat /proc/iomem loops forever.

So, just a wild guess - should there be two "struct resource"s, one for 
each platform_device, or is there some other way to break the loop in 
the tree?


Stefan Roese wrote:
> Hi Steve,
> On Friday 09 November 2007, Steven A. Falco wrote:
>> I am using the Denx 2.6.32 kernel, which does have powerpc/sequoia.
>> Xenomai is a real-time kernel built on Adeos/Ipipe.  I'll dig into it
>> further.
> Is this arch/ppc or arch/powerpc? I remember fixing this a while ago in 
> arch/ppc:
> commit 67a35ce785b1d11d09bf528c166ea26d489a4bd6
> Author: Stefan Roese <sr at denx.de>
> Date:   Thu Aug 2 14:15:22 2007 +0200
>     ppc: Fix problem with recursive NDFC platform_device resource management
>     This change fixes a problem with a resursive platform_device resource
>     management of the AMCC 4xx NDFC. Without this fix a "cat /proc/iomem"
>     leads to an infinite loop of printing the "ndfc-nand.0" resource.
>     Signed-off-by: Stefan Roese <sr at denx.de>
> Best regards,
> Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20071112/06fc8a33/attachment.htm>

More information about the Linuxppc-dev mailing list