Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and Git repository (u-boot + kernel)
Date: Thu, 21 Nov 2013 10:07:47 +0100	[thread overview]
Message-ID: <528DCD63.4060601@mind.be> (raw)
In-Reply-To: <CAAs3wMjPUqp3TBgWvteB5PO3kMN4+RarNEA9GSUUmWreJjGagg@mail.gmail.com>

On 21/11/13 09:31, Freedreamer wrote:
> Here the logs for uboot.
>
> in the folder uboot If i do command git branch I always got *master ad
> not branch i want.

  Okay... So actually everything is working perfectly.

  The uboot directory is part of buildroot, not of u-boot. Your buildroot 
is still at the master branch.

  The only way to be really certain that buildroot checked out the right 
branch is to compare the contents of output/build/uboot-* with the 
contents of your u-boot git repository.

  But since you configure u-boot for spear320_h2ad which is not in 
upstream u-boot, and that succeeds, I guess you're using the correct 
branch...

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

  parent reply	other threads:[~2013-11-21  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 12:49 [Buildroot] Buildroot and Git repository (u-boot + kernel) Freedreamer
2013-11-20 12:54 ` Thomas Petazzoni
2013-11-20 16:47   ` Freedreamer
2013-11-20 22:28     ` Arnout Vandecappelle
     [not found]       ` <CAAs3wMjPUqp3TBgWvteB5PO3kMN4+RarNEA9GSUUmWreJjGagg@mail.gmail.com>
2013-11-21  9:07         ` Arnout Vandecappelle [this message]
2013-11-21 14:27           ` Freedreamer

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=528DCD63.4060601@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