From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 9/9] manual: rework Deploying images chapter
Date: Thu, 17 Oct 2013 18:24:29 +0200 [thread overview]
Message-ID: <52600F3D.6020401@mind.be> (raw)
In-Reply-To: <CAHXCMMKzwCJbHJG-zx_7r8LavH0sJT71e12zq3p_J+GFuf8fqQ@mail.gmail.com>
On 17/10/13 10:40, Samuel Martin wrote:
> Arnout,
>
>
> 2013/10/8 Arnout Vandecappelle <arnout at mind.be <mailto:arnout@mind.be>>
>
> On 10/05/13 21:49, Samuel Martin wrote:
>
> [...]
>
> +
> +[WARNING]
> +Be careful, *the _board's_ readme files coming within Buildroot are
> +provided without warranty of any kind*.
> +They are contributions from Buildroot users, but Buildroot
> developers
> +do not ensure their correctness, nor maintain them.
>
>
> Is this warning really necessary? Most readme.txt files use
> removable media (or emulation), and the few that do write to flash
> have warnings already. The only exception is the Telit EVK-PRO3, so
> maybe we should just add a warning there.
>
> Well, the few boards we are talking about here are:
> - Telit EVK-PRO3
> - avnet s6lx9_microboard
> - freescale mpc8315erdb
> - freescale p1010rdb
> For the 2 later, there is a warning about the bootloader in the
> readme.txt files,
> for the 2 others, it is not so obvious...
For the s6lx9 the danger isn't so big because you don't overwrite the
bootloader.
>
> Anyway, I don't mind adding the warning in the readme files.
> Having it close to the flashing instruction makes sense;
> having it in the documentation (as a genreric warning) makes sense too imho.
I just don't like scaring people off... But I guess the warning doesn't
really hurt.
Regards,
Arnout
>
> Regards,
>
> --
> Samuel
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-10-17 16:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:49 [Buildroot] [pull request] Pull request for branch sma/doc-update Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 1/9] manual: minor update in manual generation Samuel Martin
2013-10-06 9:04 ` Thomas Petazzoni
2013-10-06 11:17 ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 2/9] manual: developer-guide.txt: cleanup non-existing source Samuel Martin
2013-10-06 9:04 ` Thomas Petazzoni
2013-10-08 7:51 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 3/9] manual: update dependency list to build the documentation Samuel Martin
2013-10-06 9:05 ` Thomas Petazzoni
2013-10-06 16:25 ` Thomas De Schampheleire
2013-10-06 18:21 ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 4/9] manual: add information about buildroot toolchain not being relocable and put some hints to use it Samuel Martin
2013-10-06 9:08 ` Thomas Petazzoni
2013-10-06 14:50 ` Samuel Martin
2013-10-08 9:03 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 5/9] manual: configure: add deprecation warning for Crosstool-NG toolchain backend Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 6/9] manual: introduction.txt: enhance Buildroot presentation Samuel Martin
2013-10-08 9:18 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 7/9] manual: get-involved.txt: fix event order Samuel Martin
2013-10-08 9:31 ` Thomas De Schampheleire
2013-10-08 18:04 ` Arnout Vandecappelle
2013-10-08 18:28 ` Ryan Barnett
2013-10-05 19:49 ` [Buildroot] [PATCH 8/9] manual: update get-involved section Samuel Martin
2013-10-08 9:39 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 9/9] manual: rework Deploying images chapter Samuel Martin
2013-10-08 20:29 ` Arnout Vandecappelle
2013-10-15 20:27 ` Thomas De Schampheleire
2013-10-16 21:29 ` Arnout Vandecappelle
2013-10-17 8:12 ` Thomas De Schampheleire
2013-10-17 8:18 ` Arnout Vandecappelle
2013-10-17 8:43 ` Samuel Martin
2013-10-17 8:40 ` Samuel Martin
2013-10-17 16:24 ` Arnout Vandecappelle [this message]
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=52600F3D.6020401@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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