From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: BSP advice
Date: Sun, 18 Mar 2012 17:49:18 -0600 [thread overview]
Message-ID: <4F66747E.504@balister.org> (raw)
In-Reply-To: <018b01cd0557$8bbd8740$a33895c0$@slingshot.co.nz>
On 03/18/2012 04:36 PM, R U Local wrote:
> Dear List,
>
> Is it possible to build an Angstrom rootfs without building x-load, u-boot
> and kernel image?
>
> We have a new development that uses an AM3517 based unit.
>
> The SDK comes with pre-patched source code for x-load, u-boot and kernel.
> There are also compiled binary images.
>
> To get things working quickly I'd like to build a rootfs with our software
> and dependent packages and use the supplied binaries during installation.
>
>
>
> Would setting ASSUME_PROVIDED in the machine BSP achieve this?
How are you going to handle the kernel modules?
Build something close and ignore the packages you do not need :)
Philip
prev parent reply other threads:[~2012-03-18 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 22:36 BSP advice R U Local
2012-03-18 23:49 ` 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=4F66747E.504@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