From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Xianghua Xiao <xiaoxianghua@gmail.com>
Cc: yocto@yoctoproject.org, beagleboard@googlegroups.com
Subject: Re: [beagleboard] Yocto
Date: Fri, 03 Dec 2010 14:15:33 -0500 [thread overview]
Message-ID: <4CF941D5.5030407@windriver.com> (raw)
In-Reply-To: <AANLkTinc8zq20orAerFvTz9T6CFkQe9pChAG9JwdEJTQ@mail.gmail.com>
On 10-12-03 02:11 PM, Xianghua Xiao wrote:
> On Fri, Dec 3, 2010 at 12:46 PM, Petr Štetiar<ynezz@true.cz> wrote:
>> Michael J. Hammel<mjhammel@graphics-muse.org> [2010-12-03 11:01:27]:
>>
>> Hi,
>>
>>> I've heard of Yocto only in passing. I'm assuming it's another
>>> bitbake-based metabuild system? Is there some reasoning why
>>> Meego/Linaro/OpenEmbedded/Angstrom/Custom Builds cannot fill the
>>> requirements of Yocto? I don't mean that harshly at all - I'm just
>>> curious about the evolution and true target audiences of these projects.
>>> It's nice to have choices, but developers should have some idea of the
>>> differences so they can choose wisely when just starting.
>>
>> Richard wrote nice summary[1], it's worth reading and it might answer your
>> questions as well :-)
>>
>> 1. http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-November/026598.html
>>
>> -- ynezz
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Beagle Board" group.
>> To post to this group, send email to beagleboard@googlegroups.com.
>> To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
>>
>>
>
> May we know roughly how many paid resources are behind Yocto?
>
> Which arch will be first officially supported? Will it be ATOM as Poky
> is really part of Intel? Beagle/ARM will be done by the community
> instead?
I can provide some answers for this part of the query.
In the 0.9 release, we already support the following arches:
- x86(64), mips, arm and powerpc
These are all based on a 2.6.34 kernel base (with an option
for 2.6.37-rcX shortly). There are simulated targets for
each arch, and a hardware reference for each as well
(for ARM the reference hardware is the beagleboard).
Hope that helps,
Bruce
>
> Thanks,
> Xianghua
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2010-12-03 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8A929EC0-8AF1-48BB-ACD4-9D38C8F72DCD@jonmasters.org>
[not found] ` <1291399287.16321.18.camel@feynman.coloradoengineeringinc.com>
[not found] ` <20101203184643.GW10755@ibawizard.net>
2010-12-03 19:11 ` [beagleboard] Yocto Xianghua Xiao
2010-12-03 19:15 ` Bruce Ashfield [this message]
2010-12-03 19:34 ` Xianghua Xiao
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=4CF941D5.5030407@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=beagleboard@googlegroups.com \
--cc=xiaoxianghua@gmail.com \
--cc=yocto@yoctoproject.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 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.