All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 9/9] manual: rework Deploying images chapter
Date: Wed, 16 Oct 2013 23:29:00 +0200	[thread overview]
Message-ID: <525F051C.90200@mind.be> (raw)
In-Reply-To: <CAAXf6LUspWfQkggfq2_+vmuDHUcPQUUAa6D3_-J7jxG8-0svBg@mail.gmail.com>

On 15/10/13 22:27, Thomas De Schampheleire wrote:
> Hi Samuel, Arnout,
>
> On Tue, Oct 8, 2013 at 10:29 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 10/05/13 21:49, Samuel Martin wrote:
>>>
> [..]
>>> +flashing and/or booting the given platform.
>>> +
>>> +Although, deploying the generated images on the actual hardware
>>> +(flashing and booting the hardware) is very tight to the target
>>> +hardware and can differ a lot from one target to another.
>>> +Buildroot cannot provide information on this part.
>>> +
>>> +For deploying images on the actual target, refer to the hardware
>>> +vendor instructions, or the readme file in the _board_ directory if
>>> +any.
>>
>>
>>   I don't like how these two paragraphs are formulated, but I can't readily
>> think of an improvement.
>>
>
> Maybe:
> Nevertheless, how to deploy the generated images on actual hardware is
> very board-specific. Buildroot cannot provide instructions for all
> boards, or even provide complete instructions for a single board.
> Please refer to the instructions provided by the target vendor.

  Nice!

>
> [..]
>
>
>
> Regarding the section names, currently you have:
> 4. Deploying target images built with Buildroot
> 4.1. Deploying images on the target hardware
> 4.2. Booting images in emulators
> 4.3. Preparing a raw disk image for customized target layout
> 4.4. Preparing a bootable raw disk file for virtualization
> 4.5. Booting the generated image over the network
> 4.6. Chroot into generated image
>
> While 4 and 4.1 talk about 'deploying' the other sections start using
> other terminology. Here is a suggestion:
> 4. Deploying target images built with Buildroot
> 4.1. Deploying images on the target hardware
> 4.2. Deploying images in emulators
> 4.3. Preparing a raw disk image for customized target layout
> 4.4. Preparing a bootable raw disk file for virtualization
> 4.5. Deploying images over the network
> 4.6. Chroot into generated image
>
> In fact, 4.5 also talks about target hardware, so should probably be
> moved above, or even a subsection of 4.1.
> I'm not yet a big fan of the names of 4.3, 4.4 and 4.6 (it's unclear
> to me what they really do based on the title) but I don't have good
> suggestions.

  Right, my attempt: a bit of reordering and more "deploying":

4. Deploying target images built with Buildroot
4.1. Deploying images on the target hardware
      (includes the network deployment)
4.2. Deploying images on removable media
4.3. Preparing a bootable raw disk file for virtualization
4.4. Deploying images in emulators
4.5. Chroot into generated image


  Regards,
  Arnout

-- 
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

  reply	other threads:[~2013-10-16 21:29 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 [this message]
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

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=525F051C.90200@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 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.