All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Enrico Mioso <mrkiko.rs@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [mtdblock] reading regions where %512 != 0
Date: Fri, 9 Aug 2019 14:15:44 +0200	[thread overview]
Message-ID: <20190809141544.2eb99774@collabora.com> (raw)
In-Reply-To: <alpine.LNX.2.21.99999.352.1908071924030.11090@localhost.localdomain>

Enrico,

On Wed, 7 Aug 2019 19:27:49 +0200 (CEST)
Enrico Mioso <mrkiko.rs@gmail.com> wrote:

> Hello guys!
> 
> first of all - thank you for your great work!
> 
> I've been experimenting an issue with OpenWRt on a TP-Link Archer C60 V2 device, where an mtd region has been defined so that it's not 512-bytes aligned:
> 
> mac: partition@1fb00 {
>   	label = "mac";
>   	reg = <0x01fb00 0x000500>;
>   	read-only;
> };
> 
> So the region is 1280 bytes long; still reading from the exported mtdblock device will results in a 1024 bytes read.
> This prevents users from making proper backups of flash regions. I don't know how many instances of this exist in the OpenWRt tree right now, but it's not clear wether we should fix this issue in the mtdblock or defining regions differently, changing their sizes.
> Any help, suggestions or ideas very welcome and apreciated.

Is this a NOR or a NAND? Have tried reading from the mtd device instead
of mtdblock? I guess block devices have to be aligned on 512B...

> 
> Thank you very much,
> Enrico
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-08-09 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 17:27 [mtdblock] reading regions where %512 != 0 Enrico Mioso
2019-08-09 12:15 ` Boris Brezillon [this message]
2019-08-09 12:48   ` Enrico Mioso

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=20190809141544.2eb99774@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mrkiko.rs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.