From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by ozlabs.org (Postfix) with ESMTP id C0064DDEE1 for ; Fri, 13 Feb 2009 17:30:50 +1100 (EST) Received: by wf-out-1314.google.com with SMTP id 27so1118551wfd.15 for ; Thu, 12 Feb 2009 22:30:48 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 13 Feb 2009 07:30:48 +0100 Message-ID: Subject: Re: writel hangs system From: Tobias Knutsson To: Grant Likely Content-Type: text/plain; charset=ISO-8859-1 Cc: "linuxppc-dev@ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , There seems to be some magic force linked to this mailing list. Whenever I post a question, the matter seems to resolve itself. :) In order to stay as consistent as possible with the old 2.4 kernel, I used the same mapping that they had: 0x50000000 - 0x6000000000 for memory 0x60000000 - 0x6100000000 for I/O When I changed it to the default that was in the lite5200b device tree I could access the memory regions as well. Thanks for your help! On Thu, Feb 12, 2009 at 22:18, Grant Likely wro= te: > On Tue, Feb 10, 2009 at 6:07 AM, Tobias Knutsson > wrote: >> Hello, >> >> I'm in the process of porting a PCI-driver for a dsp-board from 2.4 to >> 2.6. The probing of the driver goes well, IRQs are setup, resources >> are claimed and remapped without any problems. Reading from I/O >> regions also works well. However, when i try to read or write to a >> memory region using readl/writel, the system instantly hangs. No >> stacktrace or anything, it just stops. > > Hmmm. Not good. Are you able to access the memory regions from the > U-Boot console? > > g. > > -- > Grant Likely, B.Sc., P.Eng. > Secret Lab Technologies Ltd. > --=20 H=E4lsningar/Regards Tobias Knutsson