Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] defconfig for warpboard
Date: Sat, 20 Jun 2015 11:44:53 +0200	[thread overview]
Message-ID: <55853615.5080107@mind.be> (raw)
In-Reply-To: <55848E49.1030304@mind.be>

On 06/19/15 23:48, Arnout Vandecappelle wrote:
> On 06/19/15 17:29, Arthur LAMBERT wrote:
>> > This is a set of patch to add support for warpboard (Freescale board based on imx6sl)
>> > 
>> > Signed-off-by: Arthur LAMBERT <lambertarthur22@gmail.com>
>> > ---
>> >  configs/warpboard_defconfig | 31 +++++++++++++++++++++++++++++++
>> >  1 file changed, 31 insertions(+)
>> >  create mode 100644 configs/warpboard_defconfig
>> > 
>> > diff --git a/configs/warpboard_defconfig b/configs/warpboard_defconfig
>> > new file mode 100644
>> > index 0000000..188ea4d
>> > --- /dev/null
>> > +++ b/configs/warpboard_defconfig
>> > @@ -0,0 +1,31 @@
>> > +# architecture
>> > +BR2_arm=y
>> > +BR2_cortex_a9=y
>  Please also fix the kernel headers to a specific version. Pretty soon 4.1 will
> be the default, and they may be incompatible with the kernel you build.
> 
> 
>> > +
>> > +# system
>> > +BR2_TARGET_GENERIC_HOSTNAME="warpboard"
>> > +BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
>> > +
>> > +# kernel
>> > +BR2_LINUX_KERNEL=y
>> > +BR2_LINUX_KERNEL_CUSTOM_GIT=y
>> > +BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git at github.com:Freescale/linux-fslc.git"
>  For github, we prefer to use a wget download rather than a a git download,
> since it's a lot faster. So:
> 
> BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION=$(call
> github,Freescale,linux-fscl,38ec11d74b0fbe110b658a6e1a86eeac7e5a383e)

 As noticed by Francois, the source part of the URL should also be included, so:

BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,Freescale,linux-fscl,38ec11d74b0fbe110b658a6e1a86eeac7e5a383e)/38ec11d74b0fbe110b658a6e1a86eeac7e5a383e.tar.gz"


 Regards,
 Arnout

[snip]


-- 
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2015-06-20  9:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 15:29 [Buildroot] [PATCH 1/4] defconfig for warpboard Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 2/4] README file for wifi/bluetooth support Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 3/4] fix bluetooth support on kernel 4.0, and warpboard kernel config Arthur LAMBERT
2015-06-19 15:29 ` [Buildroot] [PATCH 4/4] firmware file for wifi Arthur LAMBERT
2015-06-19 17:20   ` Yann E. MORIN
2015-06-21  0:49     ` Arthur LAMBERT
2015-06-21 10:16       ` Yann E. MORIN
2015-06-19 21:48 ` [Buildroot] [PATCH 1/4] defconfig for warpboard Arnout Vandecappelle
2015-06-19 22:00   ` Arnout Vandecappelle
2015-06-21  1:00     ` Arthur LAMBERT
2015-06-21 13:26       ` Arnout Vandecappelle
2015-06-20  9:44   ` Arnout Vandecappelle [this message]
2015-06-21  0:56   ` Arthur LAMBERT
2015-06-21 13:32     ` Arnout Vandecappelle

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=55853615.5080107@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