All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: wangyang <wangyang01@cn.panasonic.com>
Cc: yocto@yoctoproject.org
Subject: Re: about how to port YOCTO
Date: Mon, 16 May 2011 05:19:42 -0600	[thread overview]
Message-ID: <4DD1084E.30509@mlbassoc.com> (raw)
In-Reply-To: <4DD0CDCE.4000108@intel.com>

On 05/16/2011 01: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/)

Beyond that, there are some bigger issues.  Remember that Yocto is
just packaging for a Linux kernel and the user tools that surround
it.  Before you can add a new machine, especially one with a different
architecture as the original email hints, you have to have a working
toolchain (GCC and friends), Linux kernel, GLIBC, etc.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-05-16 11: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 [this message]
     [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
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=4DD1084E.30509@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=wangyang01@cn.panasonic.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.