Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Brian Norris <briannorris@chromium.org>
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Teresa Remmet" <t.remmet@phytec.de>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Adam Ford" <aford173@gmail.com>,
	linux-mtd@lists.infradead.org,
	"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: [PATCH 1/6] ARM: dts: am335x-phycore-som: Update NAND partition table
Date: Fri, 6 Jan 2017 18:39:44 +0100	[thread overview]
Message-ID: <20170106173944.t3jq7amga3j5ahe6@lenoch> (raw)
In-Reply-To: <20170105175619.GA56877@google.com>

On Thu, Jan 05, 2017 at 09:56:20AM -0800, Brian Norris wrote:
[snip]
> The best solution would be to try to migrate away from static device
> tree representations of partition info entirely. UBI volumes are best
> where possible. If not, then some other kind of on-flash data structures
> (along the lines of a GPT) with a corresponding MTD partition parser is
> an OK alternative. Unfortunately, there isn't any good standard format
> for this on MTD, so it's typically all custom -- and so people use the
> easiest approach: device tree. And it's even more difficult with NAND,
> which has reliability problems, especially with static data (e.g., read
> disturb).

Just as a side note, there is some work in this area:
https://www.mail-archive.com/u-boot@lists.denx.de/msg232759.html

> Anyway, the parser solution is helpful only if one can properly fix the
> "flag day" first. And it requires a little bit more work to be generally
> useful; I posted some work for this over a year ago, but bikeshedding
> brought it down.

Best regards,
	ladis

      parent reply	other threads:[~2017-01-06 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1483627851-17996-1-git-send-email-t.remmet@phytec.de>
     [not found] ` <1483627851-17996-2-git-send-email-t.remmet@phytec.de>
     [not found]   ` <20170105153637.GA4310@atomide.com>
     [not found]     ` <20170105171845.GK4310@atomide.com>
2017-01-05 17:56       ` [PATCH 1/6] ARM: dts: am335x-phycore-som: Update NAND partition table Brian Norris
2017-01-06  9:27         ` Teresa Remmet
2017-01-06 16:02           ` Tony Lindgren
2017-01-06 16:05             ` Adam Ford
2017-01-06 16:14               ` Tony Lindgren
2017-01-06 18:20                 ` Brian Norris
2017-01-06 18:43                   ` Tony Lindgren
2017-01-06 17:39         ` Ladislav Michl [this message]

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=20170106173944.t3jq7amga3j5ahe6@lenoch \
    --to=ladis@linux-mips.org \
    --cc=aford173@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=briannorris@chromium.org \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=t.remmet@phytec.de \
    --cc=tony@atomide.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