[lkml]   [2017]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize

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 <>
> Signed-off-by: Chris Packham <>

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?

 \ /
  Last update: 2017-07-04 05:23    [W:0.178 / U:1.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site