linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/1] mtd: gpmi: make blockmark swapping optional
Date: Fri, 28 Mar 2014 09:16:46 +0100	[thread overview]
Message-ID: <20140328091646.1ce03f90@ipc1.ka-ro> (raw)
In-Reply-To: <5334D9F7.2030001@freescale.com>

Hi,

Huang Shijie wrote:
> ? 2014?03?27? 20:21, Lothar Wa?mann ??:
> > I can assure you that the>100.000 i.MX28 based modules, that we sold
> > up to now boot from NAND just fine without any block mark swapping in
> > the U-Boot pages.
> >
> Our driver should follow the Reference manual, not the product.
> 
Still there is no need for the Linux NAND driver to be able to read or
write partitions in a format that the Boot ROM can understand. Thus it
is perfectly legal to allow disregarding the BB marks and solely rely on
a flash based BBT.


Lothar Wa?mann
-- 
___________________________________________________________

Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996

www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________

  reply	other threads:[~2014-03-28  8:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 13:23 [PATCH] mtd: gpmi: make blockmark swapping optional y at karo-electronics.de
2014-03-20  8:33 ` Juergen Beisert
2014-03-20  9:20   ` Lothar Waßmann
2014-03-20  9:15 ` Huang Shijie
2014-03-20  9:21   ` Lothar Waßmann
2014-03-20  9:47     ` Huang Shijie
2014-03-20 10:09       ` Lothar Waßmann
2014-03-20 10:56         ` Huang Shijie
2014-03-21  5:36 ` Huang Shijie
2014-03-21 10:50   ` [PATCHv2 1/1] " Lothar Waßmann
2014-03-24  9:59     ` Huang Shijie
2014-03-26  8:51       ` Lothar Waßmann
2014-03-26 10:41         ` Huang Shijie
2014-03-26 11:55           ` Lothar Waßmann
2014-03-27  9:59             ` Huang Shijie
2014-03-27 12:21               ` Lothar Waßmann
2014-03-28  2:09                 ` Huang Shijie
2014-03-28  8:16                   ` Lothar Waßmann [this message]
2014-03-28  8:39                     ` Huang Shijie
2014-03-28  9:00                       ` Sascha Hauer
2014-03-28  9:26                         ` Huang Shijie
2014-03-28  9:31                           ` Lothar Waßmann
2014-03-28 10:09                             ` Huang Shijie
2014-03-28 10:18                               ` Lothar Waßmann
2014-03-28  9:01                       ` Lothar Waßmann
2014-03-28  9:33                         ` Huang Shijie
2014-03-28  9:38                           ` Huang Shijie
2014-03-28 10:13                             ` Lothar Waßmann
2014-03-28 10:35 ` [PATCHv3 0/2] " Lothar Waßmann
2014-03-28 10:35   ` [PATCHv3 1/2] " Lothar Waßmann
2014-03-31  2:06     ` Huang Shijie
2014-03-28 10:35   ` [PATCHv3 2/2] of/mtd/nand: add generic binding and helper for NAND_BBT_NO_OOB_BBM Lothar Waßmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140328091646.1ce03f90@ipc1.ka-ro \
    --to=lw@karo-electronics.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).