Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] board: add support for ARM Juno r1 Development Board
Date: Wed, 28 Oct 2015 22:29:46 +0100	[thread overview]
Message-ID: <56313E4A.10709@mind.be> (raw)
In-Reply-To: <5629F99E.2040105@synopsys.com>

On 23-10-15 11:10, Joao Pinto wrote:
> 
> Hi,
> 
> On 10/22/2015 9:20 PM, Arnout Vandecappelle wrote:
>> On 22-10-15 18:17, Joao Pinto wrote:
[snip]
>>> +BR2_LINUX_KERNEL=y
>>> +BR2_LINUX_KERNEL_CUSTOM_GIT=y
>>> +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="http://git.linaro.org/landing-teams/working/arm/kernel.git"
>>> +BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="6917b51dee54f21816706af2278517b7af218f9a"
>>
>>  This is just v4.3-rc1, so you could use an upstream kernel instead of Linaro.
>> Are you sure you took the right sha?
> 
> The Juno board was recently added to linux mainline (v4.2 I think) but the total
> support is still in Linaro. Take as an example the video output support, sound
> and pcie. The git commid id I configured is one of the latest, assuring that we
> have the maximum of stable functionalities as possible. The stable tags lack
> crucial features.

 The commit Id you selected _is_ v4.3-rc1, or actually, the commit just before
v4.3-rc1:

$ git describe --contains 6917b51dee54f21816706af2278517b7af218f9a
v4.3-rc1~1

$ git log -1 --pretty=format:'%H%n%s' v4.3-rc1^
6917b51dee54f21816706af2278517b7af218f9a
Merge tag 'cris-for-4.3' of
git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris


 So I think you picked the wrong commit sha.

> 
>>
>>> +BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
>>> +BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/arm/junor1/linux-junor1-defconfig"
>>> +BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y
>>> +BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image"
>>> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
>>> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="arm/juno-r1"
>>
>>  No need for a bootloader?
> 
> The board uses EDK2, which comes already built with the board.
> If a developer needs to build a custom package it should get teh edk2 package a
> built it.

 It would be nice if you could add it, but that's not a prerequisite for getting
this defconfig in. Note that edk2 should go under boot/, not package/

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-10-28 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 11:55 [Buildroot] [RESEND] [PATCH v7] board: add support for ARM Juno Development Board Joao Pinto
2015-10-22 20:20 ` [Buildroot] [PATCH v5] board: add support for ARM Juno r1 " Arnout Vandecappelle
2015-10-23  9:10   ` Joao Pinto
2015-10-28 21:29     ` Arnout Vandecappelle [this message]
2015-12-16 20:22 ` [Buildroot] [PATCH v7] board: add support for ARM Juno " Thomas Petazzoni
     [not found] ` <20160201122047.GR1194@e106497-lin.cambridge.arm.com>
2016-02-01 12:24   ` [Buildroot] [RESEND] " Joao Pinto

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=56313E4A.10709@mind.be \
    --to=arnout@mind.be \
    --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