Hi Frank, On Apr 11, 2014, at 6:35 PM, Frank Bormann wrote:
> Hi Pantos, hi Tom, > > I sent this a couple of months ago to the mailing list, never really received > a response. We are testing 2014.04-rc3 right now and the issue is still > there. Would you still consider bringing this fix in for the upcoming release? > > This is for an eMMC chip with an initial memory size > 2GB whose memory size > drops below 2GB when turning enhanced (pseudo-SLC) mode on for the user > partition. u-boot would then fail memory size detection and assume memory > size if zero. You'd see error messages like: > > MMC: block number 0x1 exceeds max(0x0) > MMC: block number 0x800 exceeds max(0x0) > MMC: block number 0x900 exceeds max(0x0) > > Thanks, > Frank > Your patch is corrupted; can you please resend and make sure it applies using git am? > panto@sles11esa:~/u-boot-mmc.git (master)$ git am -3 > U-Boot-RFC-1-1-Read-mmc-device-memory-capacity-from-EXT_CSD-if-memory-is-addressed-by-sector.patch > > Applying: Read mmc device memory capacity from EXT_CSD if memory is addressed > by sector > fatal: corrupt patch at line 50 > Repository lacks necessary blobs to fall back on 3-way merge. > Cannot fall back to three-way merge. > Patch failed at 0001 Read mmc device memory capacity from EXT_CSD if memory > is addressed by sector > The copy of the patch that failed is found in: > /home/panto/ti/u-boots/u-boot-mmc.git/.git/rebase-apply/patch > When you have resolved this problem, run "git am --resolved". > If you prefer to skip this patch, run "git am --skip" instead. > To restore the original branch and stop patching, run "git am --abort". > Regards -- Pantelis _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot