From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by ozlabs.org (Postfix) with ESMTP id F29D9DDDE7 for ; Thu, 7 Aug 2008 12:52:54 +1000 (EST) Received: by rv-out-0506.google.com with SMTP id f6so202622rvb.9 for ; Wed, 06 Aug 2008 19:52:53 -0700 (PDT) Message-ID: Date: Wed, 6 Aug 2008 22:52:53 -0400 From: vb Sender: vbendeb@gmail.com To: linuxppc-embedded@ozlabs.org Subject: Accessing peripheral bus devices on 460GT MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , I am trying to bring up a 2.6.25 based system on a 460GT platform. I am using the OF tree cloned off canyonblands.dts, and I am not sure if something is missing in the tree, or in the kernel, or I am doing something stupid. The problem is that I don't seem to be able to access any peripheral device activated by cs1, 2, 3 (I have not tried touching the NOR flash (cs0) just yet). If I don't touch any peripherals the system can netbboot or diskboot all the way to the linux prompt. But unfortunately, the damn peripherals have to be touched :-) I do invoke ioremap_nocache(, ), and it returns a virtual address. The thing is that as soon as I try accessing the device off this pointer an exception is thrown. From u-boot I can access the ..+ space no problem. I see that the dts file mentions that u-boot is supposed to supply the "ranges" property in the /plb/opb/ebc section; examining the u-boot code for different amcc platforms shows that only the NOR flash size is supplied there. I guess the real question is how do I gain access to the EBC mapped hardware configured by u-boot? can someone please shed any light on this, thanks a lot in advance, Vadim