From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: Enabling mtd partitioning layout
Date: Mon, 14 Dec 2015 13:53:53 +0100 [thread overview]
Message-ID: <20151214125352.GA5485@amd> (raw)
In-Reply-To: <201512141320.28567.marex@denx.de>
On Mon 2015-12-14 13:20:28, Marek Vasut wrote:
> On Monday, December 14, 2015 at 12:51:16 PM, Pavel Machek wrote:
> > On Mon 2015-12-14 12:31:32, Marek Vasut wrote:
> > > On Monday, December 14, 2015 at 12:26:39 PM, Pavel Machek wrote:
> > > > On Mon 2015-12-14 12:09:08, Marek Vasut wrote:
> > > > > On Monday, December 14, 2015 at 08:54:38 AM, Pavel Machek wrote:
> > > > > > (Please, trim your emails when replying)
> > > > > >
> > > > > > > Try this:
> > > > > > >
> > > > > > > mtdparts=1m(u-boot),256k(env1),256k(env2),14848k(boot),112m(root)
> > > > > > > ,- at 1 536k (UBI)
> > > > > > >
> > > > > > > This will create overlapping partitions "boot,root" and "UBI" .
> > > > > >
> > > > > > Just because you can does not mean that you should. This looks like
> > > > > > a nasty trap for a user.
> > > > >
> > > > > Please explain in detail why do you think so.
> > > >
> > > > Please make a 200 page study of human psychology explaining that noone
> > > > would ever be confused by two overlapping partitions :-).
> > >
> > > Add a comment explaining the situation and reasoning behind that, problem
> > > solved.
> >
> > We do partitions so that people don't overwrite data by
> > mistake. Having overlapping partitions kind of defeats the purpose.
>
> I'd expect that in case you are fiddling with MTD on a bootloader level, you
> have at least a vague idea of what you are doing.
Yes, but people should not have to expect we prepare traps for them.
> > Just because trap is documented does not mean that it is not
> > nasty. 199.95 pages to go.
>
> Do you have a better idea how to satisfy both sets of people, ones which want
> kernel on a separate partition and ones which want to use single UBI volume
> then ?
If you expect people to read a comments explaining a situation, you
can easily add an explanation and (commented out) alternative
configutation that can be used.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-14 12:53 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 9:15 [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: Enabling mtd partitioning layout Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 2/6] arm: socfpga: arria5-socdk: " Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 3/6] arm: socfpga: de0-nano-soc: " Chin Liang See
2015-12-11 14:21 ` Marek Vasut
2015-12-11 15:43 ` Dinh Nguyen
2015-12-11 17:36 ` Marek Vasut
2015-12-12 0:01 ` Chin Liang See
2015-12-12 21:10 ` Pavel Machek
2015-12-12 21:45 ` Marek Vasut
2015-12-13 0:01 ` Chin Liang See
2015-12-13 0:04 ` Chin Liang See
2015-12-11 9:15 ` [U-Boot] [PATCH 4/6] arm: socfpga: mcvevk: " Chin Liang See
2015-12-11 14:21 ` Marek Vasut
2015-12-11 9:15 ` [U-Boot] [PATCH 5/6] arm: socfpga: sockit: " Chin Liang See
2015-12-11 14:23 ` Marek Vasut
2015-12-11 9:15 ` [U-Boot] [PATCH 6/6] arm: socfpga: socrates: " Chin Liang See
2015-12-11 14:23 ` Marek Vasut
2015-12-11 14:21 ` [U-Boot] [PATCH 1/6] arm: socfpga: cyclone5-socdk: " Marek Vasut
2015-12-11 23:59 ` Chin Liang See
2015-12-12 3:20 ` Marek Vasut
2015-12-12 6:30 ` Chin Liang See
2015-12-12 15:36 ` Marek Vasut
2015-12-12 23:59 ` Chin Liang See
2015-12-13 0:01 ` Marek Vasut
2015-12-13 0:49 ` Chin Liang See
2015-12-13 3:14 ` Marek Vasut
2015-12-13 13:03 ` Chin Liang See
2015-12-13 15:42 ` Marek Vasut
2015-12-14 0:11 ` Chin Liang See
2015-12-14 0:22 ` Marek Vasut
2015-12-14 0:43 ` Chin Liang See
2015-12-14 0:58 ` Marek Vasut
2015-12-14 1:22 ` Chin Liang See
2015-12-14 1:25 ` Marek Vasut
2015-12-14 15:22 ` Chin Liang See
2015-12-15 0:32 ` Marek Vasut
2015-12-15 1:09 ` Chin Liang See
2015-12-15 1:15 ` Marek Vasut
2015-12-15 10:09 ` Chin Liang See
2015-12-15 18:16 ` Marek Vasut
2015-12-18 9:39 ` Chin Liang See
2015-12-18 13:10 ` Marek Vasut
2015-12-22 15:49 ` Chin Liang See
2015-12-22 15:53 ` Marek Vasut
2015-12-22 16:00 ` Chin Liang See
2015-12-22 20:10 ` Marek Vasut
2015-12-23 0:24 ` Chin Liang See
2015-12-23 0:48 ` Marek Vasut
2015-12-23 1:38 ` Chin Liang See
2015-12-23 19:02 ` Pavel Machek
2015-12-23 22:57 ` Chin Liang See
2015-12-23 23:16 ` Marek Vasut
2015-12-23 23:36 ` Chin Liang See
2015-12-24 1:30 ` Marek Vasut
2015-12-28 8:51 ` Chin Liang See
2015-12-28 12:39 ` Marek Vasut
2015-12-29 21:06 ` Chin Liang See
2015-12-29 21:20 ` Marek Vasut
2015-12-23 23:18 ` Marek Vasut
2015-12-14 7:54 ` Pavel Machek
2015-12-14 11:09 ` Marek Vasut
2015-12-14 11:26 ` Pavel Machek
2015-12-14 11:31 ` Marek Vasut
2015-12-14 11:51 ` Pavel Machek
2015-12-14 12:20 ` Marek Vasut
2015-12-14 12:53 ` Pavel Machek [this message]
2015-12-14 13:34 ` Marek Vasut
2015-12-14 15:31 ` Chin Liang See
2015-12-13 0:49 ` Chin Liang See
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=20151214125352.GA5485@amd \
--to=pavel@denx.de \
--cc=u-boot@lists.denx.de \
/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