On Sat, Aug 01, 2015 at 02:28:06AM +0200, Stefan Agner wrote:
> Did the measurement:
>
> As is:
> ...
> [ 30.955675] mtd_speedtest: testing eraseblock write speed
> [ 143.349572] mtd_speedtest: eraseblock write speed is 4641 KiB/s
> [ 143.355606] mtd_speedtest: testing eraseblock read speed
>
On 2015-08-01 01:47, Brian Norris wrote:
> On Sat, Aug 01, 2015 at 01:35:52AM +0200, Stefan Agner wrote:
>> On 2015-08-01 01:09, Brian Norris wrote:
>
>> >> +static int vf610_nfc_read_page(struct mtd_info *mtd, struct nand_chip
>> >> *chip,
>> >> + uint8_t *buf, int oob_re
On Sat, Aug 01, 2015 at 01:35:52AM +0200, Stefan Agner wrote:
> On 2015-08-01 01:09, Brian Norris wrote:
> >> +static int vf610_nfc_read_page(struct mtd_info *mtd, struct nand_chip
> >> *chip,
> >> + uint8_t *buf, int oob_required, int page)
> >> +{
> >> + int eccsize =
Hi Brian,
On 2015-08-01 01:09, Brian Norris wrote:
>> +static inline int vf610_nfc_correct_data(struct mtd_info *mtd, uint8_t *dat)
>> +{
>> +struct vf610_nfc *nfc = mtd_to_nfc(mtd);
>> +u8 ecc_status;
>> +u8 ecc_count;
>> +int flip;
>> +
>> +ecc_status = __raw_readb(nfc->regs
Again, this patch doesn't seem to have made it to the public mailing
lists. Entire context left intact:
On Fri, Jul 31, 2015 at 06:52:58PM +0200, Stefan Agner wrote:
> This adds hardware ECC support using the BCH encoder in the NFC IP.
> The ECC encoder supports up to 32-bit correction by using 60
5 matches
Mail list logo
