From: Brian Norris <computersforpeace@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Daniel Golle <daniel@makrotopia.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
dedekind1@gmail.com, Richard Weinberger <richard@nod.at>,
robh+dt@kernel.org, linux-mtd@lists.infradead.org,
dwmw2@infradead.org
Subject: Re: [PATCH 1/2] ubi: mount partitions specified in device tree
Date: Mon, 20 Jun 2016 10:05:03 -0700 [thread overview]
Message-ID: <20160620170503.GA33122@google.com> (raw)
In-Reply-To: <6411961.soYuJ4Ixfs@wuerfel>
Hi,
I'll take a moment to hijack this and solicit comments on this old
thread:
On Mon, Jun 20, 2016 at 10:09:50AM +0200, Arnd Bergmann wrote:
> - MTD partitioning unfortunately does not seem to have a widely used
> method for identifying partitions from what's stored on the flash,
> unlike block devices, so whatever we normally have in the partition
> table has to be stored in DT. This really sucks, but I don't know
> what else to do about it.
I got sidetracked, but I have attempted previously to at least diminish
the amount of MTD partitioning info that is stuck into DT:
http://lists.infradead.org/pipermail/linux-mtd/2015-December/064076.html
That series effectively accepts the fact that there isn't a single
standard or widely used method for identifying partitions, but it does
allow for a description that's at least more flexible than a static list
of partitions. I'd appreciate any thoughts on that. The main factors
that stalled that were that (a) there was some vague discomfort over the
use of the "compatible" property (I could probably have argued my case
better there) and (b) I didn't have more time to pursue that. I may pick
this up again when I get some time, especially if there are constructive
suggestions.
Brian
next prev parent reply other threads:[~2016-06-20 17:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 19:17 [PATCH 1/2] ubi: mount partitions specified in device tree Hauke Mehrtens
2016-06-18 19:17 ` [PATCH 2/2] ubi: open volumes define " Hauke Mehrtens
2016-06-18 23:36 ` Daniel Golle
2016-06-19 21:21 ` Hauke Mehrtens
2016-06-24 18:45 ` Ezequiel Garcia
2016-06-25 20:24 ` Hauke Mehrtens
2016-06-18 19:30 ` [PATCH 1/2] ubi: mount partitions specified " Richard Weinberger
2016-06-18 19:35 ` Hauke Mehrtens
2016-06-18 19:46 ` Richard Weinberger
2016-06-18 22:54 ` Hauke Mehrtens
2016-06-19 8:41 ` Richard Weinberger
2016-06-18 23:20 ` Daniel Golle
2016-06-19 8:53 ` Richard Weinberger
2016-06-19 9:16 ` Richard Weinberger
2016-06-19 11:25 ` Daniel Golle
2016-06-19 12:02 ` Richard Weinberger
2016-06-19 13:05 ` Daniel Golle
2016-06-19 13:19 ` Richard Weinberger
2016-06-19 14:09 ` Daniel Golle
2016-06-19 14:35 ` Richard Weinberger
2016-06-19 15:24 ` Daniel Golle
2016-06-19 15:31 ` Richard Weinberger
2016-06-19 16:13 ` Daniel Golle
2016-06-19 16:53 ` Boris Brezillon
2016-06-19 19:42 ` Daniel Golle
2016-06-19 20:14 ` Boris Brezillon
2016-06-19 21:48 ` Daniel Golle
2016-06-19 22:21 ` Hauke Mehrtens
2016-06-20 8:09 ` Arnd Bergmann
2016-06-20 8:26 ` Richard Weinberger
2016-06-20 15:08 ` Arnd Bergmann
2016-06-20 17:24 ` Brian Norris
2016-06-20 19:57 ` Richard Weinberger
2016-06-20 21:18 ` Hauke Mehrtens
2016-06-20 17:05 ` Brian Norris [this message]
2016-06-19 15:43 ` Boris Brezillon
2016-06-19 16:23 ` Daniel Golle
2016-06-20 17:03 ` Brian Norris
2016-06-24 18:28 ` Ezequiel Garcia
2016-06-25 20:20 ` Hauke Mehrtens
2016-06-25 20:33 ` Richard Weinberger
2016-06-18 23:56 ` Daniel Golle
2016-06-19 21:36 ` Hauke Mehrtens
2016-06-19 21:52 ` Daniel Golle
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=20160620170503.GA33122@google.com \
--to=computersforpeace@gmail.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=daniel@makrotopia.org \
--cc=dedekind1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
/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).