Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Arlott <simon@fire.lp0.eu>
To: Florian Fainelli <f.fainelli@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	Jonas Gorski <jogo@openwrt.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH linux-next] mtd: part: Add BCM962368 CFE partitioning support
Date: Thu, 10 Dec 2015 18:51:37 +0000	[thread overview]
Message-ID: <5669C9B9.1070103@simon.arlott.org.uk> (raw)
In-Reply-To: <5669B965.5030105@gmail.com>

On 10/12/15 17:41, Florian Fainelli wrote:
> Le 09/12/2015 13:55, Simon Arlott a écrit :
>>  drivers/mtd/Kconfig         |  21 +++
>>  drivers/mtd/Makefile        |   1 +
>>  drivers/mtd/bcm963268part.c | 373 ++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 395 insertions(+)
>>  create mode 100644 drivers/mtd/bcm963268part.c
> 
> What motivated created a separate partition parser rather then using the
> extended the existing one?

I started off doing that but had to split it up because how it handles
the nvram and bcm_tag to construct the partition layout is significantly
different. The nvram isn't even read from flash in bcm63xxpart, and the
psi size value isn't used by bcm963268.

> I would imagine that, at some point, the partition parser could know
> what kind of flash it needs to parse: SPI/P-NOR or NAND, and based on
> that, do an appropriate definition?

With the device tree changes Brian's introducing it can be specified in
there, otherwise a common parser would need to read from the
miscStrapBus register which would be difficult for a partition parser as
it's not a device and has no memory resources.

-- 
Simon Arlott

      reply	other threads:[~2015-12-10 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 21:55 [PATCH linux-next] mtd: part: Add BCM962368 CFE partitioning support Simon Arlott
2015-12-10 17:41 ` Florian Fainelli
2015-12-10 18:51   ` Simon Arlott [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=5669C9B9.1070103@simon.arlott.org.uk \
    --to=simon@fire.lp0.eu \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=f.fainelli@gmail.com \
    --cc=jogo@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --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