From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: (No subject)
Date: Thu, 03 Jun 2010 14:59:31 +0200 [thread overview]
Message-ID: <4C07A733.1040303@atmel.com> (raw)
In-Reply-To: <76E258664B189C4CBEF125491CA11ECC9445E0CF8C@KCINPUNHJCMS01.kpit.com>
Le 03/06/2010 14:13, Soumya R :
> Hi,
>
> MACHINE = "at91sam9263ek"
> DISTRO = "angstrom-2008.1"
>
> I am new to this open embedded so you may seem may question is silly..
> I need to know wat i need to deploy to my target and where the final image is stored..
> Please help me out.. Thanks in advance :-)
I advice you to go on
http://www.linux4sam.org
and follow the documentation there. You will have an example of the
deployment of such a distribution.
In an OE build, here are the resulting images:
tmp/deploy/glibc/images/at91sam9263ek/
- Linux kernel (as a uImage suitable for u-boot):
uImage-2.6.30-r1-at91sam9263ek.bin
- Angstrom rootfs:
Angstrom-x11-at91sam9-image-glibc-ipk-2009.X-stable-at91sam9263ek.rootfs.jffs2
For micro-image, you will find a different name but at the same location.
IPK packages are located here:
tmp/deploy/glibc/ipk/
Hope that it helps,
--
Nicolas Ferre
next prev parent reply other threads:[~2010-06-03 15:17 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 9:19 (No subject) Soumya R
2010-06-02 15:41 ` Hodgson, Simon
2010-06-03 2:37 ` Soumya R
2010-06-03 5:10 ` Khem Raj
2010-06-03 8:24 ` Hodgson, Simon
2010-10-29 11:43 ` Nick Lee
2010-06-03 12:13 ` Soumya R
2010-06-03 12:59 ` Nicolas Ferre [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-03 17:13 Ankit Navik
2018-07-23 12:28 William Delacre
2018-07-26 19:40 ` Mark Asselstine
2018-07-27 15:03 ` Mark Asselstine
2018-07-27 16:04 ` William Delacre
2018-07-27 16:16 ` Mark Asselstine
2018-07-27 16:25 ` William Delacre
2018-07-27 16:44 ` S. Lockwood-Childs
2018-07-27 16:42 ` William Delacre
2018-07-27 16:47 ` Mark Asselstine
2018-07-31 11:54 ` William Delacre
2018-07-31 14:30 ` Mark Asselstine
2018-07-31 18:46 ` S. Lockwood-Childs
2018-07-31 22:34 ` William Delacre
2018-06-06 8:05 Parthiban Nallathambi
2017-06-19 14:57 Мар'ян Пріцак
2017-06-19 19:01 ` Josef Holzmayr
2017-06-20 8:07 ` Tamtamis, Panagiotis
2017-06-20 14:07 ` Josef Holzmayr
2017-06-20 14:32 ` Tamtamis, Panagiotis
2017-06-20 14:55 ` Мар'ян Пріцак
2017-04-06 0:06 Andrej Rode
2016-02-23 0:55 Joe MacDonald
2014-07-11 14:54 Philip Balister
2014-07-12 4:55 ` Khem Raj
2013-07-31 15:07 Joe MacDonald
2012-06-21 21:36 Andreas Müller
2012-06-22 9:34 ` Henning Heinold
2012-05-01 7:57 Craig McQueen
2012-05-01 11:00 ` Radoslav Kolev
2012-02-15 12:06 Hauser, Wolfgang (external)
2011-03-01 17:45 Denis 'GNUtoo' Carikli
2011-03-01 18:25 ` Denis 'GNUtoo' Carikli
2010-07-29 10:44 Soumya R
2010-07-01 10:19 Soumya R
2010-07-01 19:04 ` Khem Raj
2010-07-02 2:50 ` Soumya R
2010-06-12 11:46 "Andreas Müller"
2010-06-10 5:56 Soumya R
2010-06-10 6:29 ` Frans Meulenbroeks
2010-06-08 8:22 Soumya R
2010-06-08 14:09 ` Khem Raj
2010-03-01 14:46 majo huber
2010-01-23 10:54 saleh usman
2009-08-03 13:18 Gregory Machairidis
2009-06-09 3:17 Rolf Leggewie
2009-06-09 3:26 ` Rolf Leggewie
2009-06-09 3:29 ` Rolf Leggewie
2009-03-19 17:59 Theodore A. Roth
2008-03-10 14:36 Lele
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=4C07A733.1040303@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=openembedded-devel@lists.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