From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Slides "Using Buildroot for real projects"
Date: Fri, 21 Oct 2011 17:25:49 +0200 [thread overview]
Message-ID: <20111021172549.2611d3a7@skate> (raw)
In-Reply-To: <4EA182BA.2050400@carallon.com>
Le Fri, 21 Oct 2011 15:33:30 +0100,
Will Wagner <will_wagner@carallon.com> a ?crit :
> Couple of minor points on the English (Still very impressive from a
> non native speaker)
Thanks!
> p8: "Buildroot starts by the toolchain" should be "starts with the"
Funny, because Will Moore told me to do the exact opposite (in a review
he sent me privately yesterday):
"""
Slide 7, "Buildroot starts with the toolchain" not "Buildroot starts by
the toolchain".
"""
Now I understand why I fail to further improve my english. It's because
it's a fuzzy logic language ! :-)
> p16 "Any other project specific file" should perhaps be "files"
I have changed to "All other project specific files", maybe it's more
correct?
> p17: "kernel and bootloaders often" shouldn't it be singular
> bootloader?
Not necessarily. On AT91 platforms, you have two bootloaders:
at91boostrap and u-boot, and I both patch them and build them within
Buildroot.
> p17: "drawback is that Buildroot does directly" unless I
> misunderstand the use case, don't you mean doesn't?
Fixed, thanks, that was a major typo.
> p21: "I don't recommend this, ..." I'm not sure if you are not
> recommending changing the skeleton or using a script to modify it
Ok, I tried to clarify it:
"""I don't recommend this solution as it consists in duplicating the
default skeleton, which would prevent from taking advantage of future
improvements of the default skeleton."""
> p30: "finds automagically" should be "automagically finds"
Fixed.
> p37: "assignements" should be assignments
Fixed.
> p37: "allows to tell" should be "allows you to tell"
Fixed.
> One thing I'd love to get written up somewhere is best practice for
> NFS mounting a filesystem image, but I realise this may not be
> relevant to your talk.
Ah, good point. I'll include a slide about this.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-21 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 16:47 [Buildroot] [RFC] Slides "Using Buildroot for real projects" Thomas Petazzoni
2011-10-17 21:13 ` Peter Korsgaard
2011-10-18 7:26 ` Baruch Siach
2011-10-21 13:44 ` Thomas Petazzoni
2011-10-18 9:22 ` Thomas De Schampheleire
2011-10-18 21:35 ` Arnout Vandecappelle
2011-10-19 6:29 ` Thomas De Schampheleire
2011-10-21 13:43 ` Thomas Petazzoni
2011-10-21 13:51 ` Yegor Yefremov
2011-10-21 13:58 ` Thomas Petazzoni
2011-10-21 14:24 ` Yegor Yefremov
2011-10-21 15:34 ` Thomas Petazzoni
2011-10-21 14:33 ` Will Wagner
2011-10-21 15:25 ` Thomas Petazzoni [this message]
2011-10-22 17:04 ` Thomas De Schampheleire
2011-10-23 12:37 ` Baruch Siach
2011-10-24 15:32 ` Thomas Petazzoni
2011-10-24 16:42 ` Yann E. MORIN
2011-10-24 17:17 ` Thomas Petazzoni
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=20111021172549.2611d3a7@skate \
--to=thomas.petazzoni@free-electrons.com \
--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.