> >> > Don't you get "010" prior to the boot content? > >> > Most cards have their EXT_CSD_PART_CONFIG_ACC_ACK bit set. > >> > So you need to eliminate it from the boot file? > >> > But your compare show that the files are identical - how so? > >> > >> By configuring the card to not send BOOT ACK. > >> With it enabled there is unfortunately no way to get the transfer > >> through from userspace. > >> (The host will sample part of the ACK, CRC wont match and so on) > > This doesn't seems to be a reasonable requirement from the average user - > e.g. validation & field application engineers who address eMMC issues as well, > but mostly other embedded flash protocols - ufs & others. > > Is it? I mean usually they configure the boot partition, too and mmc-utils gives > them all they need with: > e.g. mmc-utils bootpart enable 1 0 /dev/mmcblkX But yeah, if this is too much > of a limitation to be considered useful then this patch is not worth pursuing as > pretending the boot operation is a normal block transfer for ioctl and the host > driver only works with boot ack off. > Anything with boot ack on cannot be done from userspace and not even host- > controller-agnostic, i.e. would need its own host_ops call, which is a bit overkill > for testing / debugging purposes I'd say. OK. How about test that EXT_CSD_PART_CONFIG_ACC_ACK is not set, And bail out if it does? Thanks, Avri > > Regards, > Christian > > > Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz Managing Director: > Dr. Jan Peter Berns. > Commercial register of local courts: Freiburg HRB381782
