All of lore.kernel.org
 help / color / mirror / Atom feed
From: petter@technux.se
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] x-load: fix broken beaglebone support and FILEPATHS usage
Date: Sat, 26 Apr 2014 20:39:02 +0200	[thread overview]
Message-ID: <a39a653b557587457fa05eeb545d7d87@technux.se> (raw)
In-Reply-To: <535BB044.6030502@mlbassoc.com>

2014-04-26 15:10 skrev Gary Thomas:

> On 2014-04-25 16:11, Petter Mabäcker wrote:
>
>> The following changes since commit
>> c446d4edca3b4edfcdee48247391bfb306aab4c2: default-distrovars.inc: 
>> Add
>> libgcc-initial to the GPLv3 whitelist (same as libgcc) (2014-04-25
>> 18:00:38 +0100) are available in the git repository at:
>> git://git.yoctoproject.org/poky-contrib petmab/fix_xload
>>
> 
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/fix_xload
>> [1] Petter Mabäcker (2): x-load: fix broken beaglebone support 
>> x-load:
>> remove usage of FILESPATH 
>> .../x-load/x-load-git/beagleboard/name.patch
>> | 18 ---------- .../0001-Change-omap3530beagle-target-name.patch | 
>> 37
>> ++++++++++++++++++++ meta/recipes-bsp/x-load/x-load_git.bb | 6 ++-- 
>> 3
>> files changed, 39 insertions(+), 22 deletions(-) delete mode 100644
>> meta/recipes-bsp/x-load/x-load-git/beagleboard/name.patch create 
>> mode
>> 100644
>>
>
meta/recipes-bsp/x-load/x-load/beaglebone/0001-Change-omap3530beagle-target-name.patch
>
> These changes don't seem quite correct since the beagleboard
> wasn't renamed to be beaglebone - they are separate entities
> and there are still beagleboard(s) out there (supported by
> meta-ti)
>
> At most, your changes should simply add support for beaglebone,
> not remove support for beagleboard.
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------

Hi,

Thanks for your input. Beagleboard is not longer supported in YP. See: 
Yocto Bug #2444, that results in for example:

9680453 yocto-project-qs: Substituting Beaglebone for Beagleboard.
and
7254dfb Drop beagleboard, replaced by beaglebone

And usage of meta-ti layer to build beagleboard will override the 
x-load version within meta layer (from oe) anyway (see 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/x-load/x-load_git.bb). 
So my opinion is that it's correct to replace beagleboard with 
beaglebone in this commit. But if you have any other opinion, please let 
me know and I will of course consider them.

Anyone else who have any comments about this?

BR,
Petter

Links:
------
[1] 
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/fix_xload


  reply	other threads:[~2014-04-26 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 22:11 [PATCH 0/2] x-load: fix broken beaglebone support and FILEPATHS usage Petter Mabäcker
2014-04-25 22:11 ` [PATCH 1/2] x-load: fix broken beaglebone support Petter Mabäcker
2014-04-25 22:11 ` [PATCH 2/2] x-load: remove usage of FILESPATH Petter Mabäcker
2014-04-26 13:10 ` [PATCH 0/2] x-load: fix broken beaglebone support and FILEPATHS usage Gary Thomas
2014-04-26 18:39   ` petter [this message]
2014-04-27  9:52     ` Koen Kooi
2014-04-27 11:22       ` petter

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=a39a653b557587457fa05eeb545d7d87@technux.se \
    --to=petter@technux.se \
    --cc=openembedded-core@lists.openembedded.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.