[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170708011419.GE55942@google.com>
Date: Fri, 7 Jul 2017 18:14:19 -0700
From: Brian Norris <computersforpeace@...il.com>
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"boris.brezillon@...e-electrons.com"
<boris.brezillon@...e-electrons.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Marek Vasut <marek.vasut@...il.com>,
Richard Weinberger <richard@....at>,
Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
David Oberhollenzer <david.oberhollenzer@...ma-star.at>
Subject: Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0
erasesize
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
Powered by blists - more mailing lists