From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id DF2F3B7079 for ; Fri, 4 Sep 2009 18:52:03 +1000 (EST) Received: from casper.infradead.org (casper.infradead.org [85.118.1.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 844F9DDD01 for ; Fri, 4 Sep 2009 18:52:03 +1000 (EST) Subject: Re: [PATCH] powerpc/mpc52xx/mtd: fix mtd-ram access for 16-bit Local Plus Bus From: David Woodhouse To: Albrecht =?ISO-8859-1?Q?Dre=DF?= In-Reply-To: <1244911551.3423.0@antares> References: <1244911551.3423.0@antares> Content-Type: text/plain; charset="UTF-8" Date: Fri, 04 Sep 2009 09:51:50 +0100 Message-Id: <1252054310.4483.539.camel@macbook.infradead.org> Mime-Version: 1.0 Cc: Linux PPC Development List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2009-06-13 at 18:45 +0200, Albrecht Dreß wrote: > Am 11.06.09 19:28 schrieb(en) Grant Likely: > > So; the solution to me seems to be on an MPC5200 platform replace the > > offending hooks with MPC5200 specific variants at runtime. > > Will re-work the patch that way! BTW, a dumb question: what is the > proper way to determine which cpu the system is running on? Check the > CPU node of the of tree? Surely the solution is for it to be a 'complex' mapping, where it can provide its own I/O functions instead of polluting the inline versions designed for 'simple' maps with special cases? -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation