All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Holger Freyther <holger@freyther.de>, poky@pokylinux.org
Subject: Re: Impressions of using Poky to create a BSP
Date: Fri, 27 May 2011 13:19:22 -0700	[thread overview]
Message-ID: <4DE0074A.8050404@linux.intel.com> (raw)
In-Reply-To: <BANLkTi=rJ049XGM5DQGjKtf7QKEAjh0Nqw@mail.gmail.com>



On 05/27/2011 01:06 PM, Chris Larson wrote:
> On Fri, May 27, 2011 at 12:48 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> On 05/27/2011 10:42 AM, Holger Freyther wrote:
>>> Hi all,
>>>
>>> I hope these impressions are useful. In the last two days I added a BSP for a
>>> TI Davinci based system and I am afraid it was a bit harder than I think it
>>> should be. This is a summary of the underlying issues (without them being
>>> debugged or completely understood).
>>>
>>> meta-skeleton and BBFILES:
>>>    - Maybe it would be nice if the file glob would list *.bbappend as I think
>>>      many people want to use it.
>>>
>>> BBLAYERs and dependencies:
>>>     - I had changed BBFILES to list *.bbappend but the change didn't take
>>>       effect. I had to touch conf/local.conf to force a re-parse. So somehow
>>>       the layers config didn't end up in dependencies.
>>>
>>> fetch vs. fetch2:
>>>     - I wanted to fetch my kernel from my internal git/ssh repository. I was
>>>       not sure where to put the username (git://foo@bar or git://bar;user=foo)
>>
>> I believe the correct options would have been:
>>
>> ssh://foo@bar/path/to/repo
>> or
>> foo@bar:/path/to/repo
>>
>> with protocol=git
>>
> 
> This is backwards. The url scheme determines the fetcher to use, the
> protocol= determines the method that fetcher uses to obtain the
> sources. Holger had it correct. git:// to associate with the git
> fetcher, protocol= to ensure it uses ssh.

Doh, thanks for correcting. That explains some things for me. I had
thought a real git url was appropriate here, good to know!

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-05-27 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 17:42 Impressions of using Poky to create a BSP Holger Freyther
2011-05-27 19:14 ` Bruce Ashfield
2011-05-27 19:48 ` Darren Hart
2011-05-27 20:06   ` Chris Larson
2011-05-27 20:19     ` Darren Hart [this message]
2011-05-27 20:23       ` Chris Larson
2011-05-28 18:35   ` Robert Berger
2011-05-29  4:08     ` Bruce Ashfield
2011-05-27 20:36 ` Khem Raj

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=4DE0074A.8050404@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=holger@freyther.de \
    --cc=poky@pokylinux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.