From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: getting started - docbook
Date: Sun, 28 Oct 2007 09:42:12 +0100 [thread overview]
Message-ID: <47244B64.2030609@student.utwente.nl> (raw)
In-Reply-To: <20071027212600.GA6219@lenovo>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Farning schreef:
> On Sat, Oct 27, 2007 at 07:27:37PM +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> David Farning schreef:
>>> On Sat, Oct 27, 2007 at 01:06:59PM +0200, Tobias Pflug wrote:
>>>> on 1:
>>>> with big picture I mean there should be a description of the
>>>> "system" with its main components. Currently i think there is too
>>>> little of that, and too many use-cases. ("In order to change xyz,
>>>> apply abc to 123").
>>> I finished a rough draft of getting started this morning. I am going
>>> to let it sit for a week before looking at it again. Then I will
>>> rework as needed and submitte for review.
>>>
>>> In the mean time I am starting on a introduction chapter. This will
>>> be a very high level overview. Below is a first stab at the outline.
>> Even if 99.9% if the people use OE to build linux stuff, it is able to
>> build nonlinux targets like bare-metal stuff for the msp430
>> microcontroller and things like arm-wince-pe or arm-apple-darwin.
>
> That makes sense. Nothing special about the Linux kernel. For the
> purposes of documentation would you mind if we:
>
> 1 Studied the device - processer, memory, IO, devices....
> 2 Studied a generic Linux distribution - kernel, libs, apps, packages,
> files system....
> 3 Discussed how to use bb/oe to create a customized distro to run on a
> specific device.
I don't mind at all, since I said that's what 99% of the people do :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHJEtkMkyGM64RGpERAj1lAJwKnbjzj21rEj9TLZUfqrF0DHDQHwCgulo7
CaUokllIm5bTMLMv/dIg1Ko=
=f5+C
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-28 8:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 22:05 getting started - docbook Filippo Basso
2007-10-25 0:19 ` David Farning
2007-10-25 7:37 ` Koen Kooi
2007-10-25 12:11 ` David Farning
2007-10-25 17:34 ` Cliff Brake
2007-10-26 13:45 ` David Farning
2007-10-27 11:06 ` Tobias Pflug
2007-10-27 15:39 ` David Farning
2007-10-27 17:27 ` Koen Kooi
2007-10-27 21:26 ` David Farning
2007-10-27 22:09 ` Tobias Pflug
2007-10-28 8:06 ` Stelios Koroneos
2007-10-28 8:42 ` Koen Kooi [this message]
2007-10-31 12:26 ` Detlef Vollmann
2007-10-31 18:43 ` Tobias Pflug
2007-10-31 20:12 ` David Farning
2007-10-31 21:30 ` Filippo Basso
2007-10-31 12:34 ` Detlef Vollmann
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 3:38 David Farning
2007-10-22 7:14 ` Koen Kooi
2007-10-22 8:35 ` Koen Kooi
2007-10-23 5:01 ` David Farning
2007-10-23 7:01 ` Koen Kooi
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=47244B64.2030609@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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