From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751402AbdGQMea (ORCPT ); Mon, 17 Jul 2017 08:34:30 -0400 Received: from mail-wr0-f195.google.com ([209.85.128.195]:34926 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751281AbdGQMe2 (ORCPT ); Mon, 17 Jul 2017 08:34:28 -0400 Date: Mon, 17 Jul 2017 14:34:24 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Richard Weinberger Cc: Pavel Machek , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Artem Bityutskiy , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/5] mtd: block2mtd: Add support for specifying MTD write size and subpage shift Message-ID: <20170717123424.GD16493@pali> References: <1496418222-23483-1-git-send-email-pali.rohar@gmail.com> <1496418222-23483-3-git-send-email-pali.rohar@gmail.com> <20170605112145.GE14675@pali> <20170605112508.GF14675@pali> <79f3b92f-5be4-8d46-985d-0b38cffd6032@nod.at> <20170618100626.GC20211@amd> <8440a46a-0ba2-b00f-e55b-d0a0fa9b8aa6@nod.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8440a46a-0ba2-b00f-e55b-d0a0fa9b8aa6@nod.at> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sunday 18 June 2017 12:11:40 Richard Weinberger wrote: > Pavel, > > Am 18.06.2017 um 12:06 schrieb Pavel Machek: > > Hi! > > > >>>>>> Am 02.06.2017 um 17:43 schrieb Pali Rohár: > >>>>>>> It is needed for creating emulated devices suitable for using in UBI layer > >>>>>>> and with UBIFS. > >>>>>> > >>>>>> Why? > >>>>> > >>>>> ubifs depends on write size of nand. And without those parameters as > >>>>> specified in cover letter I'm unable to mount N900 rootfs image exported > >>>>> via block2mtd. ubifs reject such image. > >>>> > >>>> Hmm, so you render block2mtd into a semi-NAND chip? :) > >>> > >>> Probably you can call it like that. But it is still MTD device... > >> > >> This is what I meant in my other mail. > >> You add NAND specific properties but still denote it as MTD_RAM/ROM. > >> I'm not sure whether this is a good idea. > > > > Can you suggest any other way for Pali to mount rootfs image on his > > PC? > > Are you my micro manager? ;-) > > As stated in my other mail, we have nandsim and there is work going on > to allow specifying arbitrary NAND sizes. > An alternative approach can be found here: > https://lkml.org/lkml/2016/5/12/296 > > Thanks, > //richard Back to the this patch series. There are also other patches in this series. If you at least comment/review other patches if this one is "problematic"? -- Pali Rohár pali.rohar@gmail.com