All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Kashyap Gada <gada.kashyap@gmail.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building for Boards not supported by Yocto Project
Date: Thu, 5 Jun 2014 10:44:17 -0400	[thread overview]
Message-ID: <53908241.1060003@windriver.com> (raw)
In-Reply-To: <CANJXcUYmMp5SzgBsr3icysjVqBDr8Ksz41141r1KQ6rtKSAUMQ@mail.gmail.com>

On 14-06-05 07:28 AM, Kashyap Gada wrote:
> Hello.
>
> I have successfully built and tested core-image-sato through the process
> given by the quick start guide at the yocto project website. Now I
> intend to build an image for a board which is not officially supported
> by yocto project. I have a FriendlyArm mini6410 whose BSP is available
> for linux.
>
> I would like to know how should I proceed further.
> Is it possible to use the same BSP without any changes and make an image
> using Yocto?

Using the Yocto BSP guide 
(http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html)
as a reference, you can create a minimal BSP layer for the board.

You don't have to do everything in the guide, but you do need to
have a machine definition, the userspace tuning and a custom kernel
recipe for the platform (i.e. you point at some vendor or project
tree that has all the required patches).

Unless the support for the board is already in the mainline kernel, and
then you can have a custom linux-yocto recipe to leverage the existing
configuration and code in the linux-yocto repository.

Cheers,

Bruce

>
> Kashyap Gada
>
>



      reply	other threads:[~2014-06-05 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 11:28 Building for Boards not supported by Yocto Project Kashyap Gada
2014-06-05 14:44 ` Bruce Ashfield [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=53908241.1060003@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=gada.kashyap@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.