Re: [Q] SW-ECC to HW-ECC (OMAP3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/8/5 Grazvydas Ignotas <notasas@xxxxxxxxx>:
> On Thu, Aug 4, 2011 at 1:55 PM, Arno Steffen
> <arno.steffen@xxxxxxxxxxxxxx> wrote:
>> While migrating from .33 to .37 kernel I found, that HW-ECC is used by default.
>> I found that this is set in omap2.c:
>>        pdata->ecc_opt          = OMAP_ECC_HAMMING_CODE_HW;
>> Unfortunatly setting it back to
>>        pdata->ecc_opt          = OMAP_ECC_HAMMING_CODE_DEFAULT;
>> doesn't prevent me from getting messages like:
>>
>> uncorrectable error :
>> uncorrectable error :
>> mtd->read(0xd18 bytes from 0x7eae8) returned ECC error
>>
>> So what else has to be set? I couldn't found it.
>
> swecc on .37 is broken (I'm not even sure hwecc works as I use swecc),
> you need at least 2.6.39.1 to use that. It is possible to patch .37
> but I don't have list of needed parches, but maybe could get you that
> if you really need it (or look what changed under drivers/mtd between
> those versions yourself).
>
>> Other way maybe to keep it at HW-ECC. Is this significant faster than SW-ECC?
>> But howto get nandwrite (mtd-utils) or fw_setenv (uboot) to handle HW-ECC?
>> Do I have to use just the --noecc option?
>>
>> When using the fw_setenv command I get CRC errors in environment with next boot.
>
> Never tried hwecc so can't help you here.
>
>
> --
> Gražvydas
>

Thanks for this advice. I will check this.
Best regards
Arno
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux