public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Thu, 07 Nov 2013 15:27:23 +0100	[thread overview]
Message-ID: <527BA34B.2000807@gmail.com> (raw)
In-Reply-To: <20131107133159.GR5925@bill-the-cat>

Dear Tom Rini,

On 11/07/2013 02:31 PM, Tom Rini wrote:
> On Thu, Nov 07, 2013 at 10:37:24AM +0100, Andreas Bie?mann wrote:
>> Hello all together,
>>
>> On 11/07/2013 09:17 AM, Heiko Schocher wrote:
>>> Am 06.11.2013 08:50, schrieb Wolfgang Denk:
> [snip]
>>>> So when you're once again doing some change that requires touching
>>>> files for some othe rboards, you could simply check that database.  If
>>>> you see that 3 out of the last 5 releases have reported succesful
>>>> run-time tests you will probably decide to accept the needed efforts,
>>>
>>> Hmm.. that works, if you have to touch some (some < 5) boards. But
>>> If you have to touch > 5 boards, this gets unhandy...
>>
>> How about:
>>
>> MAKEALL --check-boards -s at91
>>
>> ;)
> 
> I feel this is the hard part of the problem, and what we're glossing
> over.  What has to be tested by the board maintainer?  What are we going
> to leave to their discretion?  Will am335x_evm not count if I don't dig
> up the NOR cape for it?

for the time being I'd glad to see reports of (un)successful boot with
configured bootm command.

But I see your point, there is another input vector for the tests. I
think this could only be defined on a per board basis.
To pick up your example, I think it is worth to know that one tested the
am335x_evm to boot via NAND. At least for the maintainer, so he can skip
that and just test the NOR booting.

Best regards

Andreas Bie?mann

  reply	other threads:[~2013-11-07 14:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 13:05 [U-Boot] livetime of boards Heiko Schocher
2013-11-05 20:37 ` Tom Rini
2013-11-06  7:50   ` Wolfgang Denk
2013-11-07  8:17     ` Heiko Schocher
2013-11-07  9:37       ` Andreas Bießmann
2013-11-07 10:39         ` Heiko Schocher
2013-11-07 11:13           ` Albert ARIBAUD
2013-11-07 11:42             ` Heiko Schocher
2013-11-07 12:06               ` Wolfgang Denk
2013-11-07 12:21                 ` Heiko Schocher
2013-11-07 11:24           ` Andreas Bießmann
2013-11-07 11:52             ` Heiko Schocher
2013-11-07 12:12               ` Wolfgang Denk
2013-11-07 12:50                 ` Heiko Schocher
2013-11-07 19:19                   ` Wolfgang Denk
2013-11-08  5:31                     ` Heiko Schocher
2013-11-08  7:19                       ` Wolfgang Denk
2013-11-07 12:01             ` Wolfgang Denk
2013-11-07 12:16               ` Andreas Bießmann
2013-11-07 12:46               ` Heiko Schocher
2013-11-07 19:15                 ` Wolfgang Denk
2013-11-08  5:28                   ` Heiko Schocher
2013-11-08  6:20                     ` Wolfgang Denk
2013-11-08  7:11                       ` Heiko Schocher
2013-11-07 13:31         ` Tom Rini
2013-11-07 14:27           ` Andreas Bießmann [this message]
2013-11-07 19:26           ` Wolfgang Denk
2013-11-07 20:51             ` Tom Rini
2013-11-07 21:06               ` Wolfgang Denk
2013-11-08  5:35             ` Heiko Schocher
2013-11-08  4:58           ` Heiko Schocher

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=527BA34B.2000807@gmail.com \
    --to=andreas.devel@googlemail.com \
    --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