Sorry for the confusion,
i realized the card i use in the old kernel board is 8G, the one in
kernel 3.17.0 is 4G,
so the size / inodes i see in mkfs or fdisk are correct.
I can confirm i have issues on the "write" part. With whatever FS,
if i format the card on PC, and then
fsck on the arm device board with kernel 3.17.0, fsck find no errors.
While if i mkfs on kernel 3.17.0 and then put the card on PC, it can't
even be mounted,
and fsck gives errors.
I finally run mmc_test, in both PIO 4-bit and DMA 4-bit modes:
in PIO, all tests pass except 17
[root@barix boot]# echo 17 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 17. Correct xfer_size at write (midway failure)...
mmc0: Result: ERROR (-84)
mmc0: Tests completed
in DMA, test 17 fails too, and test 25 locks up.
[root@barix boot]# echo 17 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 17. Correct xfer_size at write (midway failure)...
mmc0: Result: ERROR (-84)
mmc0: Tests completed.
[root@barix boot]# echo 25 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 25. Best-case read performance into scattered pages...
edma-dma-engine edma-dma-engine.1: edma_prep_slave_sg: Failed to
allocate slot
so seems i have some additional dma issue.
regards
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
