From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] out of tree kernel patches question
Date: Fri, 17 Nov 2017 21:24:17 +0100 [thread overview]
Message-ID: <20171117212417.43162ed7@windsurf.lan> (raw)
In-Reply-To: <trinity-0d97f4a0-c1ac-416e-bfea-7bcafcb3ce1d-1510924577452@3c-app-mailcom-bs07>
Hello,
On Fri, 17 Nov 2017 14:16:17 +0100, daggs wrote:
> when it comes to the odroidc2 support, there are 3 things that I'm concerned about:
> 1. gcc is limited to 4.9.x
> 2. old uboot (2005.11).
> 3. very old kernel (3.14.79).
>
> #1 is needed because #2, currently upstream uboot support this board
> from 2007.05 but I've tried for months to get upstream uboot to work
> with the vendor's kernel without any luck. unfortunately, the uboot
> mailing list isn't helpful at all (no one seems to care much), this
> means that in order to solve issue #2, the kernel needs to be
> upgraded.
> latest upstream kernel holds bask support for this board, the
> development is progressing. now assuming that I take patches existing
> in the kernel mailing list that adds missing support for features in
> the kernel to a point that the board can be used in a decent manner,
> what is the policy of adding out of the kernel patches to a board in
> buildroot?
We are generally OK to integrate kernel patches if they are merged
upstream already, or seriously on their way upstream. Also, we can do
this only if the stack of patches is not several hundreds of patches.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-17 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:16 [Buildroot] out of tree kernel patches question daggs
2017-11-17 20:24 ` Thomas Petazzoni [this message]
2017-11-18 7:43 ` daggs
2017-11-18 8:26 ` Peter Korsgaard
2017-11-18 12:10 ` daggs
2017-11-20 20:34 ` daggs
2017-11-20 20:50 ` Thomas Petazzoni
2017-11-17 21:33 ` Peter Korsgaard
2017-11-18 7:47 ` daggs
2017-11-18 8:02 ` Peter Korsgaard
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=20171117212417.43162ed7@windsurf.lan \
--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