From: "Rogério Brito" <rbrito@ime.usp.br>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Old regression with MTD devices disappearing from a Kurobox HD/HG
Date: Tue, 7 Apr 2015 22:13:00 -0300 [thread overview]
Message-ID: <20150408011300.GA6395@ime.usp.br> (raw)
In-Reply-To: <1428454204.22867.497.camel@freescale.com>
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
next prev parent reply other threads:[~2015-04-08 1:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 5:40 Old regression with MTD devices disappearing from a Kurobox HD/HG Rogério Brito
2015-04-07 22:34 ` Scott Wood
2015-04-07 23:58 ` Rogério Brito
2015-04-08 0:02 ` Scott Wood
2015-04-08 0:37 ` Rogério Brito
2015-04-08 0:50 ` Scott Wood
2015-04-08 1:13 ` Rogério Brito [this message]
2015-04-08 1:27 ` ) Scott Wood
2015-04-08 1:56 ` Old regression with MTD devices disappearing from a Kurobox HD/HG Rogério Brito
2015-04-09 21:54 ` Rogério Brito
2015-04-09 22:28 ` Scott Wood
2015-04-09 23:12 ` Rogério Brito
2015-04-16 22:55 ` Rogério Brito
2015-04-16 23:27 ` Scott Wood
2015-04-17 0:01 ` Rogério Brito
2015-04-17 0:03 ` Scott Wood
2015-04-17 0:14 ` Rogério Brito
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150408011300.GA6395@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).