Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1680645 > unrolled thread

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

Started byChris Packham <Chris.Packham@alliedtelesis.co.nz>
First post2017-07-04 05:30 +0200
Last post2017-07-08 03:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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

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

FromChris Packham <Chris.Packham@alliedtelesis.co.nz>
Date2017-07-04 05:30 +0200
SubjectRe: [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize
Message-ID<tZmHf-2yO-1@gated-at.bofh.it>
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?

[toc] | [next] | [standalone]


#1683500

FromBrian Norris <computersforpeace@gmail.com>
Date2017-07-08 03:20 +0200
Message-ID<u0MzF-3Su-11@gated-at.bofh.it>
In reply to#1680645
On Tue, Jul 04, 2017 at 03:22:52AM +0000, Chris Packham wrote:
> 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.

Wouldn't be that surprising. mtdinfo is actually developed under the
"ubi-utils" directory of mtd-utils, and UBI wouldn't know what to do
with and SRAM like that.

Brian

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web