<br><font size=2 face="sans-serif">Hi Stefan</font>
<br>
<br><font size=2 face="sans-serif">Thanks for your answer</font>
<br>
<br><font size=2 face="sans-serif">I am planning to use the U-Boot to load
the Linux operating system that is stored on a NAND flash.</font>
<br>
<br><font size=2 face="sans-serif">The UBoot main role (beside other tasks)
is to load the linux kernel and file-system from the NAND flash to the
RAM, and start the linux. </font>
<br><font size=2 face="sans-serif">Another role of UBoot is to get the
kernel and file-system from the ethernet, and burn it to the NAND flash.</font>
<br>
<br><font size=2 face="sans-serif">What is the preferred way to treat the
"bad block" problem in writing (not writing to bad blocks, and
checking the status after programming/erasing) and reading (jumping over
bad blocks).</font>
<br>
<br><font size=2 face="sans-serif">1) Does normal read/write coop with
these issues?</font>
<br>
<br><font size=2 face="sans-serif">2) In the NAND documentation it says
that the "shipped bad blocks" have to be checked prior to any
erase operations. Does the UBoot leave the bad blocks untouched during
the erase operation?</font>
<br>
<br><font size=2 face="sans-serif">3) Do you recommend to use JFFS2 file-system
just to save/read the kernel/file-system images?</font>
<br>
<br><font size=2 face="sans-serif">Sincerely</font>
<br>
<br><font size=2 face="sans-serif">Shai Lifshitz</font>
<br><font size=2 face="sans-serif">email: shail@visonic.com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Stefan Roese <sr@denx.de></b></font>
<br><font size=1 face="sans-serif">Sent by: u-boot-users-bounces@lists.sourceforge.net</font>
<p><font size=1 face="sans-serif">08/06/2007 02:12 PM</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
u-boot-users@lists.sourceforge.net</font>
<br><font size=1 face="sans-serif"> cc:
Shai Lifshitz <ShaiL@visonic.com></font>
<br><font size=1 face="sans-serif"> Subject:
Re: [U-Boot-Users] NAND "bad block"
support</font></table>
<br>
<br>
<br><font size=2><tt>On Sunday 05 August 2007, Shai Lifshitz wrote:<br>
> how does the U-Boot solve the "bad block" problem in the
NAND flash<br>
> memory?<br>
<br>
Yes, U-Boot NAND driver is bad block aware (would be worthless without).<br>
<br>
> 1) does the U-Boot have support to 'bad-block table'? If it does,
then how<br>
> do I activate it?<br>
<br>
No, the bad-block-table is not supported right now. Would be nice extension
<br>
though.<br>
<br>
> 2) does the U-Boot work with JFFS2 (that handles 'bad blocks')?<br>
<br>
Yes.<br>
<br>
Best regards,<br>
Stefan<br>
<br>
=====================================================================<br>
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev
Zundel<br>
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany<br>
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de<br>
=====================================================================<br>
<br>
-------------------------------------------------------------------------<br>
This SF.net email is sponsored by: Splunk Inc.<br>
Still grepping through log files to find problems? Stop.<br>
Now Search log events and configuration files using AJAX and a browser.<br>
Download your FREE copy of Splunk now >> http://get.splunk.com/<br>
_______________________________________________<br>
U-Boot-Users mailing list<br>
U-Boot-Users@lists.sourceforge.net<br>
https://lists.sourceforge.net/lists/listinfo/u-boot-users<br>
<br>
</tt></font>
<br>