public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
	linux-mtd@lists.infradead.org,
	David Woodhouse <David.Woodhouse@intel.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: bcm47xxpart: support TRX data partition being UBI
Date: Wed, 7 Jan 2015 12:32:45 -0800	[thread overview]
Message-ID: <20150107203245.GL9759@ld-irv-0074> (raw)
In-Reply-To: <1417456220-22815-1-git-send-email-zajec5@gmail.com>

On Mon, Dec 01, 2014 at 06:50:20PM +0100, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>

Pushed to l2-mtd.git. Thanks.

But one question below.

> ---
>  drivers/mtd/bcm47xxpart.c | 28 ++++++++++++++++++++++++++--
>  1 file changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/mtd/bcm47xxpart.c b/drivers/mtd/bcm47xxpart.c
> index cc13ea5..26a4a4a 100644
> --- a/drivers/mtd/bcm47xxpart.c
> +++ b/drivers/mtd/bcm47xxpart.c
> @@ -40,6 +40,7 @@
>  #define ML_MAGIC2			0x26594131
>  #define TRX_MAGIC			0x30524448
>  #define SQSH_MAGIC			0x71736873	/* shsq */
> +#define UBI_EC_MAGIC			0x23494255	/* UBI# */
>  
>  struct trx_header {
>  	uint32_t magic;
> @@ -50,7 +51,7 @@ struct trx_header {
>  	uint32_t offset[3];
>  } __packed;
>  
> -static void bcm47xxpart_add_part(struct mtd_partition *part, char *name,
> +static void bcm47xxpart_add_part(struct mtd_partition *part, const char *name,
>  				 u64 offset, uint32_t mask_flags)
>  {
>  	part->name = name;
> @@ -58,6 +59,26 @@ static void bcm47xxpart_add_part(struct mtd_partition *part, char *name,
>  	part->mask_flags = mask_flags;
>  }
>  
> +static const char *bcm47xxpart_trx_data_part_name(struct mtd_info *master,
> +						  size_t offset)
> +{
> +	uint32_t buf;
> +	size_t bytes_read;
> +
> +	if (mtd_read(master, offset, sizeof(buf), &bytes_read,
> +		     (uint8_t *)&buf) < 0) {
> +		pr_err("mtd_read error while parsing (offset: 0x%X)!\n",
> +			offset);
> +		goto out_default;
> +	}
> +
> +	if (buf == UBI_EC_MAGIC)

Are there any endianness issues here? You're reading in byte-by-byte,
but you then treat it like a normal 32-bit word. I guess the markers are
always written in native endianness?

> +		return "ubi";
> +
> +out_default:
> +	return "rootfs";
> +}
> +
>  static int bcm47xxpart_parse(struct mtd_info *master,
>  			     struct mtd_partition **pparts,
>  			     struct mtd_part_parser_data *data)
> @@ -186,8 +207,11 @@ static int bcm47xxpart_parse(struct mtd_info *master,
>  			 * we want to have jffs2 (overlay) in the same mtd.
>  			 */
>  			if (trx->offset[i]) {
> +				const char *name;
> +
> +				name = bcm47xxpart_trx_data_part_name(master, offset + trx->offset[i]);
>  				bcm47xxpart_add_part(&parts[curr_part++],
> -						     "rootfs",
> +						     name,
>  						     offset + trx->offset[i],
>  						     0);
>  				i++;

Brian

      reply	other threads:[~2015-01-07 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 17:50 [PATCH] mtd: bcm47xxpart: support TRX data partition being UBI Rafał Miłecki
2015-01-07 20:32 ` Brian Norris [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=20150107203245.GL9759@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=David.Woodhouse@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=zajec5@gmail.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