Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize

From	Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Newsgroups	linux.kernel
Subject	Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize
Date	2017-07-04 05:30 +0200
Message-ID	<tZmHf-2yO-1@gated-at.bofh.it> (permalink)
References	<tNLrH-3yD-3@gated-at.bofh.it> <tNLrI-3yD-23@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi,

On 02/06/17 15:21, Chris Packham wrote:
> erasesize is meaningful for flash devices but for SRAM there is no
> concept of an erase block so erasesize is set to 0. When partitioning
> these devices instead of ensuring partitions fall on erasesize
> boundaries we ensure they fall on writesize boundaries.
> 
> Helped-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>

I had someone mention to me in passing that mtdinfo was failing for them 
(crashing with some floating point error). I'm wondering if we've 
created a divide-by-zero problem by reporting 0 erase size in /proc/mtd. 
I don't have any other info and right now I don't have access to the 
system I had with the mchp23lcv1024 sram.

Andrew, do you still have access to your device?

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0  erasesize Chris Packham <Chris.Packham@alliedtelesis.co.nz> - 2017-07-04 05:30 +0200
  Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0  erasesize Brian Norris <computersforpeace@gmail.com> - 2017-07-08 03:20 +0200

csiph-web