From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nm47-vm10.bullet.mail.bf1.yahoo.com (nm47-vm10.bullet.mail.bf1.yahoo.com [216.109.114.219]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id AF36A1A0B37 for ; Wed, 8 Apr 2015 11:13:06 +1000 (AEST) Date: Tue, 7 Apr 2015 22:13:00 -0300 From: =?utf-8?Q?Rog=C3=A9rio?= Brito To: Scott Wood Subject: Re: Old regression with MTD devices disappearing from a Kurobox HD/HG Message-ID: <20150408011300.GA6395@ime.usp.br> References: <20150404054022.GA15572@ime.usp.br> <1428446044.22867.475.camel@freescale.com> <20150407235812.GA3443@ime.usp.br> <1428451332.22867.490.camel@freescale.com> <20150408003638.GA5170@ime.usp.br> <1428454204.22867.497.camel@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <1428454204.22867.497.camel@freescale.com> Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, Scott. On Apr 07 2015, Scott Wood wrote: > On Tue, 2015-04-07 at 21:37 -0300, Rogério Brito wrote: > > I see. If I do some "archaeology" (read: bisect when it stopped > > working), would that help to discover how the flash is connected? > > It will probably give you the address and size of the flash, which is > good enough to get something working. Does your config (for the old > kernel) have anything with PHYSMAP in it? I suspect it probably broke > with commit dcb3e137ce9be1dfc86e306182b23e3ae5e239c4 ("[MTD] physmap: > make physmap compat explicit"). Here is what my 2.6.27 kernel has in the section regarding physmap: ,---- | # | # Mapping drivers for chip access | # | # CONFIG_MTD_COMPLEX_MAPPINGS is not set | CONFIG_MTD_PHYSMAP=y | CONFIG_MTD_PHYSMAP_START=0xffc00000 | CONFIG_MTD_PHYSMAP_LEN=0x400000 | CONFIG_MTD_PHYSMAP_BANKWIDTH=1 | # CONFIG_MTD_PHYSMAP_OF is not set | # CONFIG_MTD_INTEL_VR_NOR is not set | # CONFIG_MTD_PLATRAM is not set `---- Here is what my 4.0-rc6 kernel has: ,---- | # | # Mapping drivers for chip access | # | # CONFIG_MTD_COMPLEX_MAPPINGS is not set | CONFIG_MTD_PHYSMAP=y | CONFIG_MTD_PHYSMAP_COMPAT=y | CONFIG_MTD_PHYSMAP_START=0xffc00000 | CONFIG_MTD_PHYSMAP_LEN=0x400000 | CONFIG_MTD_PHYSMAP_BANKWIDTH=1 | CONFIG_MTD_PHYSMAP_OF=y | # CONFIG_MTD_INTEL_VR_NOR is not set | # CONFIG_MTD_PLATRAM is not set `---- I may try to revert locally that patch here to see if things improve or not, but it will take me some time to compile it (I hope not much). Thanks, -- Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br