use invd instead of wbinvd in real mode start code

[Andy Shevchenko]

On Mon, Feb 17, 2020 at 2:31 PM Andy Shevchenko
<andy.shevchenko at gmail.com> wrote:
>
> ---------- Forwarded message ---------
> From: Andy Shevchenko <andy.shevchenko at gmail.com>
> Date: Mon, Feb 17, 2020 at 2:31 PM
> Subject: use invd instead of wbinvd in real mode start code
> To: Masahiro Yamada <masahiroy at kernel.org>, Simon Glass
> <sjg at chromium.org>, Bin Meng <bmeng.cn at gmail.com>
>
>
> Hi!
>
> It seems Masahiro's patches (don't know yet which one out of two,
> probably invd one) broke the boot on Intel Edison.

Before patches:
...
DRAM:  980.6 MiB
WDT:   Started with servicing (60s timeout)
MMC:   mmc at ff3fc000: 0, mmc at ff3fa000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Saving Environment to MMC... Writing to redundant MMC(0)... OK
Saving Environment to MMC... Writing to MMC(0)... OK
Net:   No ethernet found.
Hit any key to stop autoboot:  0


After them (v2020.04-rc2):
...
DRAM:  sfi: failed to locate SYST table
sfi: failed to locate SYST table
16 EiB


>
> Reverting (both for now) helps.
>
> Please, revert or fix ASAP before v2020.04 release!
>
> P.S. I dunno how it has been tested, so, if you have Intel Edison in
> possession, please, don't forget to test on it. It's not first time
> the Intel Edison behaviour is broken due to poor testing.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
> --
> With Best Regards,
> Andy Shevchenko



-- 
With Best Regards,
Andy Shevchenko