Philippe Mathieu-Daudé <f4...@amsat.org> writes:
> As it is legal to WRITE/ERASE the address/block 0,
> change the value of this definition to an illegal
> address: UINT32_MAX.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4...@amsat.org>
> ---
> Cc: Dr. David Alan Gilbert <dgilb...@redhat.com>
> Cc: Markus Armbruster <arm...@redhat.com>
>
> Same problem I had with the pflash device last year...
> This break migration :(
> What is the best way to do this?
Remind me: did we solve the problem with pflash, and if yes, how?
> ---
> hw/sd/sd.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/sd/sd.c b/hw/sd/sd.c
> index 30ae435d669..4c05152f189 100644
> --- a/hw/sd/sd.c
> +++ b/hw/sd/sd.c
> @@ -53,7 +53,7 @@
>
> #define SDSC_MAX_CAPACITY (2 * GiB)
>
> -#define INVALID_ADDRESS 0
> +#define INVALID_ADDRESS UINT32_MAX
>
> typedef enum {
> sd_r0 = 0, /* no response */
> @@ -666,8 +666,8 @@ static int sd_vmstate_pre_load(void *opaque)
>
> static const VMStateDescription sd_vmstate = {
> .name = "sd-card",
> - .version_id = 1,
> - .minimum_version_id = 1,
> + .version_id = 2,
> + .minimum_version_id = 2,
> .pre_load = sd_vmstate_pre_load,
> .fields = (VMStateField[]) {
> VMSTATE_UINT32(mode, SDState),
