From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] OrangePi PC addition to build root
Date: Wed, 27 Jan 2016 21:58:10 +0100 [thread overview]
Message-ID: <20160127215810.6270bb5f@free-electrons.com> (raw)
In-Reply-To: <1450962484-90787-1-git-send-email-echaudron@xiot.nl>
Eelco,
On Thu, 24 Dec 2015 14:08:04 +0100, Eelco Chaudron wrote:
> +BR2_LINUX_KERNEL=y
> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/jwrdegoede/linux-sunxi.git"
> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="a516ac6dda21e6f5edceecd08b475b16e360656b"
Your defconfig for the OrangePi PC no longer works. You used a specific
commit from Hans De Goede repository, but his branches are not stable
(i.e he is constantly rebasing them). So the commit
a516ac6dda21e6f5edceecd08b475b16e360656b no longer exists.
Could you send a patch to update the defconfig to use the mainline
4.5-rc1 kernel, which according to my colleague Maxime Ripard, contains
the support for the Orange Pi PC platform ?
You can see the failure caused by the current defconfig at
https://travis-ci.org/buildroot/buildroot-defconfig-testing/jobs/105029977.
Note that if you try to rebuild the defconfig on your side, it may work
because you have linux-a516ac6dda21e6f5edceecd08b475b16e360656b.tar.gz
in your $(BR2_DL_DIR). But new users using your defconfig are no longer
able to download this kernel version.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-27 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 13:08 [Buildroot] [PATCH 1/1] OrangePi PC addition to build root Eelco Chaudron
2015-12-28 17:08 ` Thomas Petazzoni
2016-01-27 20:58 ` Thomas Petazzoni [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=20160127215810.6270bb5f@free-electrons.com \
--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