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


Groups > linux.kernel > #1668574 > unrolled thread

Re: [PATCH 2/5] mtd: block2mtd: Add support for specifying MTD write size and subpage shift

Started byPavel Machek <pavel@ucw.cz>
First post2017-06-18 12:10 +0200
Last post2017-06-18 12: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 2/5] mtd: block2mtd: Add support for specifying MTD write  size and subpage shift Pavel Machek <pavel@ucw.cz> - 2017-06-18 12:10 +0200
    Re: [PATCH 2/5] mtd: block2mtd: Add support for specifying MTD write  size and subpage shift Richard Weinberger <richard@nod.at> - 2017-06-18 12:20 +0200

#1668574 — Re: [PATCH 2/5] mtd: block2mtd: Add support for specifying MTD write size and subpage shift

FromPavel Machek <pavel@ucw.cz>
Date2017-06-18 12:10 +0200
SubjectRe: [PATCH 2/5] mtd: block2mtd: Add support for specifying MTD write size and subpage shift
Message-ID<tTFjz-3Kq-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [next] | [standalone]


#1668576

FromRichard Weinberger <richard@nod.at>
Date2017-06-18 12:20 +0200
Message-ID<tTFtf-3Nz-1@gated-at.bofh.it>
In reply to#1668574
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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web