From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Thu, 7 Nov 2013 15:51:33 -0500 [thread overview]
Message-ID: <20131107205133.GT5925@bill-the-cat> (raw)
In-Reply-To: <20131107192657.659383811DF@gemini.denx.de>
On Thu, Nov 07, 2013 at 08:26:57PM +0100, Wolfgang Denk wrote:
> 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.
>
> 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.
>
> 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.
>
> I think we all agree that _any_ kind of test information will be
> better than none.
What we need to be careful of here is making sure whatever we grow is
both useful and not overly complicated. What I honestly wonder about is
automated testing for commands (crc32 pops to mind only because I just
fixed things) but otherwise having things broken down into a front end
where people select what they did "Booted a ___ into ___ via ___",
provide some output from a command (maybe add just a touch more info to
'version') and cover non-boot testing with copy/paste'able drop-downs.
I know automated testing is The Thing, but given N frameworks, everyone
of them has issues because frankly, every SoC family has its own quirks
about how boot and load and what is and is not even feasible, especially
for the bootloader.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131107/66b988cc/attachment.pgp>
next prev parent reply other threads:[~2013-11-07 20:51 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 [this message]
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=20131107205133.GT5925@bill-the-cat \
--to=trini@ti.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