From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problem using output of console-image
Date: Wed, 06 Jan 2010 11:26:07 -0500 [thread overview]
Message-ID: <4B44B99F.9050508@balister.org> (raw)
In-Reply-To: <BAY127-W279A13B86B227AAF2D8080D8720@phx.gbl>
On 01/06/2010 10:25 AM, saleh usman wrote:
>
> Hi
> I've built console-image for omap5912osk machine but I am facing problem in using output.There are four folders named all, armv5te, i686, omap5912osk in /temp/deploy/glibc/ipk.and so many ipk files in these folders.
> Which files exactly I should use to run the output on my target platform and how to run these files.
> Wheather to install these files, any other package or directly run them just by typing their names.
> Since
> linux is running on ARM9 GPP of machine ,should I take care of u-boot, kernel version or
> anything else to run generated output on my target platform
The file console-image* in tmp/deploy/.../images/omap5912osk/ will have
copies of the root file system in various formats. The directories you
mention are in tmp/deploy/..../ipks.
Philip
>
> Saleh
> _________________________________________________________________
> Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you.
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
prev parent reply other threads:[~2010-01-06 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 15:25 Problem using output of console-image saleh usman
2010-01-06 15:34 ` Gary Thomas
2010-01-06 16:26 ` Philip Balister [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=4B44B99F.9050508@balister.org \
--to=philip@balister.org \
--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