public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Fri, 08 Nov 2013 06:35:23 +0100	[thread overview]
Message-ID: <527C781B.6070705@denx.de> (raw)
In-Reply-To: <20131107192657.659383811DF@gemini.denx.de>

Hello Wolfgang,

Am 07.11.2013 20:26, schrieb Wolfgang Denk:
> Dear Tom,
>
> In message<20131107133159.GR5925@bill-the-cat>  you wrote:
>>
>> 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?
>
> Good question.  Eventually this is something that develops over time.

Yes, let us go step by step.

> Intially, we might be satisfied with a very basic "it works" message,
> which may just mean that this specific version booted on the actual
> hardware.
>
> In the long run, we might provide a more detailed questionaire to the
> reported.  I could for example imagine a tool that parses the board's
> config file and then provides some checkboxes - if there is NOR flash
> configured on the board, ask if NOR has been tested; similar for
> network, MMC, USB, ... other features.

Cool... and we can maybe start testscripts based on this information...
(Huch... I am sure I am sitting in Front of my PC and not sleeping
  anymore)

> One day we might even have more developers using automatic test tools
> so we could generate information on a per-command base.
>
> I know that I'm just dreaming, but we should try to just be open for
> any such future extensions, even if we start really small now.

Maybe we add in tools a directory, where we add such tests?
But this would be another big discussion...

> I think we all agree that _any_ kind of test information will be
> better than none.

Yes.

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  parent reply	other threads:[~2013-11-08  5:35 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
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 [this message]
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=527C781B.6070705@denx.de \
    --to=hs@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