From: Pedro Sanchez <psanchez@fosstel.com>
To: yocto@yoctoproject.org
Subject: Re: about how to port YOCTO
Date: Mon, 16 May 2011 10:19:21 -0400 [thread overview]
Message-ID: <4DD13269.7080606@fosstel.com> (raw)
In-Reply-To: <4DD0CDCE.4000108@intel.com>
On 05/16/2011 03:10 AM, Yu Ke wrote:
> on 2011-5-16 11:31, wangyang wrote:
>> Hello!
>>
>> Because YOCTO supports x86, arm and so on MCU. I just want to know
>> about how to
>> port YOCTO to other MCU. Is it difficult, what's kind of knowledge
>> needed?
>> Thanks
>>
>
> Add another machine is not that difficult, as Yocto is designed to be
> highly customizable for different H/W. What you need is a BSP layer for
> your H/W, it is basically the H/W specific configuration, e.g. the
> kernel config, graphics config.
>
> the BSP Guide
> (http://www.yoctoproject.org/docs/bsp-guide/bsp-guide.html) has good
> info on how to write BSP. Also you can find some example from existing
> BSP, like meta-intel BSP
> (http://git.pokylinux.org/cgit/cgit.cgi/meta-intel/)
>
> Regards
> Ke
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
When I clone the yocto git repo (git://git.pokylinux.org/poky.git) I
don't get any of these meta-xxx directories that the BSP guide talks
about. They seem to be kept in a separate git repository.
My question is then, once I create my meta-xxx directory structure, how
is it hooked up to the overall poky build infrastructure? I've failed to
find an answer in the BSP guide so far.
Thanks,
--
Pedro
next prev parent reply other threads:[~2011-05-16 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 3:31 about how to port YOCTO wangyang
2011-05-16 7:10 ` Yu Ke
2011-05-16 11:19 ` Gary Thomas
[not found] ` <000401cc1430$9cd014d0$6f93c20a@psdcd.local>
2011-05-17 11:11 ` Gary Thomas
2011-05-18 0:52 ` wangyang
2011-05-16 14:19 ` Pedro Sanchez [this message]
2011-05-16 15:07 ` Tom Zanussi
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=4DD13269.7080606@fosstel.com \
--to=psanchez@fosstel.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.