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:31:55 +0200 [thread overview]
Message-ID: <20131003173155.388ef2b4@skate> (raw)
In-Reply-To: <CA+TH9V=zwoQoHmMcgNooxDRim0G4TmB70tyXZybeFW_Na9q-hQ@mail.gmail.com>
Dear Angelo Compagnucci,
On Thu, 3 Oct 2013 17:15:50 +0200, Angelo Compagnucci wrote:
> > 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.
>
> Yep. That was the problem. I'm aware of the kernel programming in
> general (I have a driver in mainline tree), but cannot understand if
> simply copying some spare patches was the way. Probably I should force
> the kernel version in the configuration, is this correct?
Correct.
> > 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.
>
> Yes, it's weird. Probably the best way is to make myself a git kernel
> tree with these patches applied.
Either that, or even the number of patches is quite small, add them to
board/olimex/<boardname>/ as I suggested above. I believe we don't like
much to have board support that depend on 'personal' Git trees, and
these trees are unlikely to be updated.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-03 15:31 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
2013-10-03 15:15 ` Angelo Compagnucci
2013-10-03 15:31 ` Thomas Petazzoni [this message]
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=20131003173155.388ef2b4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox