linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/gpmi : add BBT support
Date: Mon, 30 Jan 2012 13:27:41 +0100	[thread overview]
Message-ID: <201201301327.41298.marek.vasut@gmail.com> (raw)
In-Reply-To: <20120130114131.GC15596@pengutronix.de>

> CCing Marek, he can say more about the U-Boot side probably...

Thanks!

> 
> > > Bootloaders may also need to write to NAND. So, they need to share the
> > 
> > Do you mean the uboot may write something to the NAND?
> > Could you show me some more detail cases?
> 
> U-Boot has NAND support in mainline, for barebox it is work-in-progress.

Why don't you rather start hacking on u-boot instead of chasing behind it all 
the time ;-)

> Both can and do write to NAND (kernel, rootfs), because both have
> established procedures to do so (and maybe don't want to rely on
> third-party tools like kobs-ng).

I think the FSL U-Boot can write stuff to NAND too. You can give that a shot 
too.
> 
> > > share the same information then. To be on the safe side regardings
> > 
> > The kobs-ng which burns the bootloader to the NAND will also burn the
> > whole BBT
> > to the NAND too.
> 
> Did it always do that? Or is a newer version needed?

I can't comment on this one, I never used it. I rather got NAND working 
properly.

> 
> > But if the bootloader can make some block bad, the BBT information
> > becomes different.
> > Does the bootloader have the feature to make some block bad?
> 
> Sure. If you are able to write NAND, you should be able to mark blocks
> bad, too :)

Not really, but you prefer to do so ;-)

Thanks!

M
> 
> Thanks,
> 
>    Wolfram

  reply	other threads:[~2012-01-30 12:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  4:36 [PATCH] mtd/gpmi : add BBT support Huang Shijie
2012-01-30  9:46 ` Wolfram Sang
2012-01-30 10:32   ` Huang Shijie
2012-01-30 10:44     ` Wolfram Sang
2012-01-30 11:29       ` Huang Shijie
2012-01-30 11:41         ` Wolfram Sang
2012-01-30 12:27           ` Marek Vasut [this message]
2012-01-30 13:12             ` Wolfram Sang
2012-01-30 13:30               ` Marek Vasut
2012-01-30 13:41                 ` Wolfram Sang
2012-01-30 14:33                   ` Marek Vasut
2012-01-31  8:47           ` Huang Shijie
2012-01-31  9:24             ` Wolfram Sang
2012-01-31  9:38               ` Huang Shijie
2012-01-31 11:37               ` Marek Vasut
2012-01-31 11:49                 ` Wolfram Sang
2012-01-31 12:21                   ` Marek Vasut
2012-01-30 12:24         ` Marek Vasut
2012-01-30 13:19           ` Wolfram Sang
2012-01-30 13:35             ` Marek Vasut

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=201201301327.41298.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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).