From: Scott Wood <scottwood@freescale.com>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Old regression with MTD devices disappearing from a Kurobox HD/HG
Date: Tue, 7 Apr 2015 19:02:12 -0500 [thread overview]
Message-ID: <1428451332.22867.490.camel@freescale.com> (raw)
In-Reply-To: <20150407235812.GA3443@ime.usp.br>
On Tue, 2015-04-07 at 20:58 -0300, Rogério Brito wrote:
> Dear Scott.
>
> First of all, thank you so very much for your reply.
>
> On Apr 07 2015, Scott Wood wrote:
> > On Sat, 2015-04-04 at 02:40 -0300, Rogério Brito wrote:
> > > ,----
> > > | physmap platform flash device: 00400000 at ffc00000
> > > | physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x000004 Chip ID 0x00007e
> > > | Amd/Fujitsu Extended Query Table at 0x0040
> > > | Amd/Fujitsu Extended Query version 1.3.
> > > | physmap-flash.0: Swapping erase regions for top-boot CFI table.
> > > | number of CFI chips: 1
> > > `----
> > >
> > > I note that arch/powerpc/boot/dts/kuroboxH{D,G}.dts have, as one of their
> > > first lines, the following comment: [0][1]
> > >
> > > XXXX add flash parts, rtc, ??
> > >
> > > [0]: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/boot/dts/kuroboxHD.dts?id=1cced5015b171415169d938fb179c44fe060dc15#n17
> > > [1]: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/boot/dts/kuroboxHG.dts?id=1cced5015b171415169d938fb179c44fe060dc15#n17
> > >
> > > Is this a problem that can be fixed via additions to the DTS files? Or
> > > would the problem be solved in a different way?
> >
> > What are your bootargs?
>
> My kernel command line is (specified via uboot) is the following:
>
> ,----
> | root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32
> `----
>
> Only that.
>
> > I suggest putting the flash device into the dts (instead of using
> > physmap), and specifying the partitions on the command-line using
> > mtdparts.
>
> This is good to know. Is there any reasonable dts that I can copy/adapt?
I'm not familiar with how flash is connected on this chip, so I don't
have a specific recommendation other than to read the binding and look
at several examples.
> I just started to read on the syntax of the dts files and I am still
> not confident that I can write my own without messing everything.
>
> Another question: would putting the description of the flash device into the
> dts file be helpful to remove any code from the kernel?
If you currently have a custom flash map driver, you could get rid of
that, but I suspect that's already gone away due to the fact that it's
no longer working.
-Scott
next prev parent reply other threads:[~2015-04-08 0:02 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 [this message]
2015-04-08 0:37 ` Rogério Brito
2015-04-08 0:50 ` Scott Wood
2015-04-08 1:13 ` Rogério Brito
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=1428451332.22867.490.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rbrito@ime.usp.br \
/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).