16:36 <webczat> and mmc guys don't seem to care about my discard question :D

16:37 <webczat> hmm or i am not subscribed to the list and they did not do reply all

22:51 <webczat> xdarklight: well what do you need? erase test on anything mainline including uboot or specifically using kernel driver? because from what i can tell, the mmc drivers in kernel just set a cap and do not actually implement erase specially, so it should work for both or for none. and what i have done (uboot does not have a erase cap so erase works there) is trying to erase the whole emmc except first

22:51 <webczat> 1mbib because boot firmware lies there... i actually deliberately gave it more blocks to erase than it has because I do not have any way to check mmc block count and I have discovered that for some reason the emmc chip or whatever does not error out when you try to erase a non existent block. unless I do not know something

22:51 <webczat> *mib

22:51 <webczat> well

22:55 <webczat> xdarklight: I have also tried the following on u-boot: I filled memory range from 0x2000000 to +512 bytes with 0xFF. and wrote that range to emmc block 0x800. i then verified if it was written correctly by clearing that memory range and rereading, and then erased the block using mmc erase command, and reread it to the same range. it was all 0's from what I can tell so i assume erase works\

22:59 <webczat> xdarklight: tried again and confirmed.

23:01 <webczat> i just hope i haven't dramatically decreased my emmc's life

23:01 <webczat> except if I would break emmc itself