Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Huang Shijie <b32955@freescale.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH resend] ubi: attach: do not return -EINVAL if the mtd->numeraseregions is 1
Date: Fri, 14 Feb 2014 13:22:54 +0200	[thread overview]
Message-ID: <1392376974.12215.78.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20140214091148.GA30044@shlinux2.ap.freescale.net>

On Fri, 2014-02-14 at 17:11 +0800, Huang Shijie wrote:
> But if we do not have any _slave_ partitions, we will only have one
> master partition.
> and the numeraseregions is kept. this is the case i meet.

Why you prefer to change UBI instead of changing MTD so that master
partitions with no slave partitions would have numeraseregions=0.

And frankly, I did not clearly understand your answer.

And what erase regions have to do with master/slave?

Correct me if I am wrong below.

The erase region concept belongs to the flash chip. Some chips have
special regions, for some special purposes, and these, typically small,
regions have a bit different geometry.

Master/slave is a purely software concept. I never clearly understood
the model, but this is something related to partitions. We have a master
MTD device representing the entire chip, and slave MTD devices
representing partitions.

In your explanation you mix these 2 unrelated concepts, and I do not
understand why.

Yes, I could go and dig the code, but I prefer the patch submitter to
educate me instead, and demonstrate the depth of his understanding of
the subject :=) Sorry, I am lazy :-)

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2014-02-14 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  8:08 [PATCH resend] ubi: attach: do not return -EINVAL if the mtd->numeraseregions is 1 Huang Shijie
2014-02-14  9:18 ` Artem Bityutskiy
2014-02-14  9:11   ` Huang Shijie
2014-02-14 11:22     ` Artem Bityutskiy [this message]
2014-02-19 11:40       ` Huang Shijie

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=1392376974.12215.78.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=b32955@freescale.com \
    --cc=linux-mtd@lists.infradead.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