From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
Roger Quadros <rogerq@ti.com>,
"Leto, Enrico" <enrico.leto@siemens.com>
Subject: Re: Passing NAND mtdparts to OMAP2+ Kernel
Date: Tue, 28 Mar 2017 21:57:05 +0200 [thread overview]
Message-ID: <20170328215705.438d7af8@bbrezillon> (raw)
In-Reply-To: <CAHCN7xJoVF+3HjHwaS_U=jDqmU_Yv201KJSQ2s8N0gSNVR8pdQ@mail.gmail.com>
+Roger and Enrico
On Tue, 28 Mar 2017 10:43:01 -0500
Adam Ford <aford173@gmail.com> wrote:
> I posted this on the linux-omap list, and I was asked to post this on
> the linux-mtd list:
>
>
> I tried to remove the MTD partitions from the Linux device tree, and I
> noticed that there was no partition information being pushed anymore
> unless I changed the mtdparts name in U-Boot.
>
> It appears as if the MTD drivers have changed a bit. I found a few
> e-mails floating around that attempt to fix this
>
> Commit f7a8e38f07a17be907585 ("mtd: nand: assign reasonable default
> name for NAND drivers") attempts to address this, and someone over at
> https://patchwork.ozlabs.org/patch/707065/ attempted to address it as
> well in a slightly different way.
Can you test the patch and let me know if solves the problem. If it
does, I'll send a clean version of the patch and queue it for 4.12.
Thanks,
Boris
next prev parent reply other threads:[~2017-03-28 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 15:43 Passing NAND mtdparts to OMAP2+ Kernel Adam Ford
2017-03-28 19:57 ` Boris Brezillon [this message]
2017-03-29 11:39 ` Adam Ford
2017-03-29 12:41 ` Roger Quadros
2017-03-29 13:10 ` Boris Brezillon
2017-03-29 13:18 ` Boris Brezillon
2017-03-29 14:06 ` Roger Quadros
2017-03-29 19:59 ` Adam Ford
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=20170328215705.438d7af8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=aford173@gmail.com \
--cc=enrico.leto@siemens.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.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