public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: use invd instead of wbinvd in real mode start code
Date: Wed, 19 Feb 2020 14:14:31 +0100	[thread overview]
Message-ID: <20200219131431.C826B240036@gemini.denx.de> (raw)
In-Reply-To: <7d480cee-88aa-f4e3-7e3d-8740bbdcc224@denx.de>

Dear Heiko,

In message <7d480cee-88aa-f4e3-7e3d-8740bbdcc224@denx.de> you wrote:
>
> > How the feed back line is organized? I mean how host system will know that
> >   a) we done flash correctly?
> >   b) the booted image is bad or good?
>
> For both questions the answer is, that you need to write a testcase
> which answer this question.
>
> For a) you flash the image in some way through U-Boot commands. You
> start this commands from a tbot testcase written in python and parse
> the output and/or return code of the command and than decide ...
>
> Same for b) reboot the board, check if new version is installed
> by parsing the U-Boot bootlog, than start U-Boot commands to find
> out, if current installed version is good or bad.

Maybe it would be nice for people who don't know tbot if you could
link to some examples for such testcases?  I think this should even
be covered in the tbot docs?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If ignorance is bliss, why aren't there more happy people?

  parent reply	other threads:[~2020-02-19 13:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHp75VdtevMO=AWeZZ-kfmo0Dx5RrGBZEW8Mm5ubLU2pm3Nh=g@mail.gmail.com>
2020-02-17 12:31 ` Fwd: use invd instead of wbinvd in real mode start code Andy Shevchenko
2020-02-17 12:33   ` Andy Shevchenko
     [not found] ` <CAK7LNASQuuEWCypyK+TDYa1eYk__KKRZ1Z8JgsEbhd+4KNFNjw@mail.gmail.com>
     [not found]   ` <CAHp75Veri=85osuFy0xDukEKN9zAULJpk+1sTdHynTL_deK=0Q@mail.gmail.com>
2020-02-17 13:47     ` Andy Shevchenko
2020-02-17 13:52       ` Bin Meng
2020-02-17 14:00         ` Andy Shevchenko
2020-02-17 14:49           ` Bin Meng
2020-02-17 15:31             ` Andy Shevchenko
2020-02-17 15:09       ` Wolfgang Denk
2020-02-17 15:13         ` Tom Rini
2020-02-17 15:32         ` Andy Shevchenko
2020-02-17 15:33           ` Andy Shevchenko
2020-02-17 16:02             ` Tom Rini
2020-02-17 16:04           ` Wolfgang Denk
2020-02-18  5:48             ` Heiko Schocher
2020-02-18 10:45               ` Andy Shevchenko
2020-02-18 11:06                 ` Heiko Schocher
2020-02-18 11:29                   ` Andy Shevchenko
2020-02-18 14:43                     ` Tom Rini
2020-02-18 15:37                       ` Andy Shevchenko
2020-02-19 13:14                   ` Wolfgang Denk [this message]
2020-02-19 13:42                     ` Tom Rini
2020-02-19 14:04                       ` Heiko Schocher
2020-02-17 16:05           ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200219131431.C826B240036@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox