<div>Hi Stefan, </div>
<div> </div>
<div>Sure I will post it to mailing list and try your suggestions.</div>
<div> </div>
<div>Thanks and Regards</div>
<div>Srinath</div>
<div> </div>
<div><br> </div>
<div><span class="gmail_quote">On 12/10/07, <b class="gmail_sendername">Stefan Roese</b> <<a href="mailto:sr@denx.de">sr@denx.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Srinath,<br><br>one note in front. Please send such questions to the mailing list. So a lot of<br>other talented people have to opportunity answer our questions.
<br><br>On Monday 10 December 2007, Srinath Iyengar wrote:<br>> I have an arm based board which can have one of the following serial<br>> flashes<br>><br>><br>> 8 MB flash with 64K sector size<br>><br>> 16 MB flash with 64K sector size
<br>> 16 MB flash with 265K sector size<br>><br>><br>> *My objective is to have a single u-boot binary (Image) which can handle<br>> any of these flashes.*<br><br>Should be possible with the CFI driver.<br>
<br>> Currently I have found the means to get it work with compile time option to<br>> differentiate between 64KB and 256KB sector size of Flash.<br>><br>> I am finding it difficult to fix the issues with CFG_FLASH_SECT_SIZE
<br>> and CFG_ENV_SECT_SIZE<br>> or CFG_ENV_SIZE values dynamically.<br><br>Correct. Currently this is not supported.<br><br>> (There should be some means by which I can determine CFG_FLASH_SECT_SIZE,<br>> eventually CFG_ENV_SECT_SIZE and CFG_ENV_SIZE
<br>> after knowing the details about FLASH (probe).Even though we are filling<br>> flash_info structure data after probing about flash we still have to live<br>> with<br>> compile time option for finding CFG_FLASH_SECT_SIZE, CFG_ENV_SECT_SIZE and
<br>> dependent Macros)<br><br>Yes, a dynamic sector size configuration would be good.<br><br>> Please let me know if my requirement is conflating with U-boot design<br>> objectives in handling flash and any suggestions to fix this issue.
<br><br>An easy way to handle all your flash chips in one image (without this dynamic<br>sector size detection) would be, if you set the CFG_ENV_SECT_SIZE to the max<br>size you can have, that is 256k. You should set CFG_ENV_SIZE to a smaller
<br>size, something like 16k, so that saving the environment doesn't take too<br>long.<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: <a href="mailto:office@denx.de">office@denx.de</a><br>=====================================================================
<br></blockquote></div><br>