All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Advice on a board support
Date: Thu, 3 Oct 2013 17:06:27 +0200	[thread overview]
Message-ID: <20131003170627.2cdd2a94@skate> (raw)
In-Reply-To: <CA+TH9V=EdvEv4UF1s-ad9EoFCUBZHaoEqgiyqB1wsBUhETJZiQ@mail.gmail.com>

Dear Angelo Compagnucci,

On Thu, 3 Oct 2013 14:39:14 +0200, Angelo Compagnucci wrote:

> Recently I discovered the OLinuxIno nano board form Olimex and I
> really loved every corner of that!
> 
> Now I really want to build a rootfs with buildroot, but unfortunately
> I discovered the board is not supported.
> 
> I really would like to contribute to the buildroot project supporting
> this board, but this will be my first contribution. I read several
> docs and I have a last question open.
> 
> To make this board fully operative, several patches should be applied
> to some specific versions of the linux kernel. Patches are ready
> available[1] but how integrate them with boildroot?
> 
> So my question is: what is the recommended way to support this new platform?

As explained in
http://buildroot.org/downloads/manual/manual.html#customize-store-board-support,
adding the support for a board in Buildroot is a matter of creating a
minimal working configuration. You can also look at the existing
configurations in Buildroot for other boards.

The Git tree you pointed at is unfortunately not a kernel Git tree
which you can directly point Buildroot at. It's a tree that contains
kernel patches, so Buildroot cannot do much with this. However, since
the number of patches is rather small, you can simply copy them in
Buildroot in board/olimex/<boardname>/, and point Buildroot to this
directory for the kernel patches.

Note that the patches in this tree look a bit weird: there are some
patches for AT91 SOCs, and some other patches for i.MX SOCs.

Another option is to find a real kernel Git tree that works for your
platform. Or even better, the mainline kernel!

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-03 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 12:39 [Buildroot] Advice on a board support Angelo Compagnucci
2013-10-03 15:06 ` Thomas Petazzoni [this message]
2013-10-03 15:15   ` Angelo Compagnucci
2013-10-03 15:31     ` Thomas Petazzoni
2013-10-03 17:02 ` François Perrad
2013-10-03 19:56   ` Angelo Compagnucci

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=20131003170627.2cdd2a94@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.