All of lore.kernel.org
 help / color / mirror / Atom feed
From: ran shalit <ranshalit@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Q: nand usage
Date: Fri, 18 Mar 2011 11:54:43 -0700 (PDT)	[thread overview]
Message-ID: <31184035.post@talk.nabble.com> (raw)
In-Reply-To: <20110318184250.71829EA440@gemini.denx.de>




wd wrote:
> 
> 
>> I think my question was not very well expressed. I ment to ask about the
>> mapping of the partitions inside the NAND: Does each partitions need some
>> spare blocks (padding block) becuase of the bad block skipping in the
>> Nand ?
>> As I said, I did not find any information about the strategy of mapping
>> partitions in the Nand. 
> 
> As you are talking about partitions, I assume you refert to the MTD
> partitioning.  In this case the bad block handling needs to be done in
> by the file system code, when you create a file system insinde one of
> the partitions.
> 
> [Note that this differs from UBI, where bad block handling is done for
> the whole device, independent of the volumes that you create on top of
> it.]
> 
> 

Sorry, I probably use the wrong terms in my question. I do not mean
partition using file system,
but just saving files using the u-boot interface, for example saving the
kernel file in some space in the NAND and for the u-boot file in another
space in the NAND, and all done with the given write command in the uboot
(nand write...). And again with this u-boot interface I still need some
strategy for deciding where to put each file.

Thanks again,

Ran
-- 
View this message in context: http://old.nabble.com/-U-Boot--Q%3A-nand-usage-tp31178552p31184035.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2011-03-18 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  4:27 [U-Boot] Q: nand usage Ran Shalit
2011-03-18 16:35 ` Wolfgang Denk
2011-03-18 18:19   ` ran shalit
2011-03-18 18:42     ` Wolfgang Denk
2011-03-18 18:54       ` ran shalit [this message]
2011-03-18 19:15         ` Scott Wood

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=31184035.post@talk.nabble.com \
    --to=ranshalit@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.