From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Tue, 05 Nov 2013 14:05:28 +0100 [thread overview]
Message-ID: <5278ED18.3050105@denx.de> (raw)
Hello all,
We have the real problem, that we have a lot of old boards, which
are unmaintained in U-Boot, and we have no chance to find out, if this
boards are longer used/tested ...
So, the question raises, should we introduce a column in boards.cfg,
which shows the "livetime" of a board support in U-Boot?
If we introduce this, we init the livetime column in boards.cfg with
a value of n for all current boards, or if we add a new board support.
(n releases valid) I think n = 4 would be a good starting point.
Every release cycle the livetime value gets decremented by one.
(Can be done by a script sitting in the tools directory?)
livetime == 0 -> EMail to board maintainer, that board livetime ends.
please test and send an update, if board support should
remain in U-Boot.
livetime == -1 -> board gets deleted in next release
If a board maintainer gets the above EMail, or of course whenever
he really try a current release on a real hardware, he can send a patch,
which updates the livetime column again back to n ...
So, the hope is, we have after n releases only real tested and used
boards in U-Boot...
What do others think?
short ToDo list:
- make an initial patch for boards.cfg
- make a script, which decrements the "livetime" column in boards.cfg
and send an EMail for the "livetime == 0" case to the boardmaintainer
and make a delete patch for boards.cfg if "livetime == -1" ?
- add a doc/README.livetime
bye,
heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next reply other threads:[~2013-11-05 13:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 13:05 Heiko Schocher [this message]
2013-11-05 20:37 ` [U-Boot] livetime of boards 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
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=5278ED18.3050105@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.