From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Tue, 19 Aug 2014 22:02:04 +0200 (CEST) Received: from elvis.franken.de ([193.175.24.41]:60700 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S6855328AbaHSUB0bk8ZN (ORCPT ); Tue, 19 Aug 2014 22:01:26 +0200 Received: from uucp (helo=solo.franken.de) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1XJpat-00060S-02; Tue, 19 Aug 2014 22:01:23 +0200 Received: by solo.franken.de (Postfix, from userid 1000) id 7FD061D270; Tue, 19 Aug 2014 22:01:15 +0200 (CEST) Date: Tue, 19 Aug 2014 22:01:15 +0200 From: Thomas Bogendoerfer To: Ralf Baechle Cc: Joshua Kinard , Linux MIPS List Subject: Re: [PATCH] MIPS: IP28: Correct IO_BASE in mach-ip28/spaces.h for proper ioremap Message-ID: <20140819200115.GA13326@alpha.franken.de> References: <53F2BC86.8000506@gentoo.org> <20140819080034.GA11547@linux-mips.org> <20140819100502.GA5321@alpha.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140819100502.GA5321@alpha.franken.de> User-Agent: Mutt/1.5.21 (2010-09-15) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 42152 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: tsbogend@alpha.franken.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Tue, Aug 19, 2014 at 12:05:02PM +0200, Thomas Bogendoerfer wrote: > On Tue, Aug 19, 2014 at 10:00:34AM +0200, Ralf Baechle wrote: > I'll give a spin later. after fixing the L1_CACHE_SHIFT my IP28 booted successfull to a shell prompt. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]