All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Cliff Brake <cbrake@bec-systems.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [diasy] omap2plus_defconfig does not include systemd support
Date: Mon, 14 Jul 2014 16:26:48 -0400	[thread overview]
Message-ID: <20140714202648.GX15788@edge> (raw)
In-Reply-To: <CAOd_LFysd8sM+-PU54eEDSNCs=A2tr83yMoZMvpQ-CsutwJCTg@mail.gmail.com>

On Fri, Jul 11, 2014 at 12:24:15PM -0400, Cliff Brake wrote:
> On Fri, Jul 11, 2014 at 12:08 PM, Dmytriyenko, Denys <denys@ti.com> wrote:
> > Unless you also have meta-yocto-bsp layer (before daisy) defining
> > beagleboard machine...
> 
> or unless you have meta-gumstix-community included ...
> 
> DEBUG: LOAD /scratch/oe/oe-build-daisy/sources/meta-ti/conf/machine/beagleboard.conf
> DEBUG: CONF /scratch/oe/oe-build-daisy/sources/meta-ti/conf/machine/beagleboard.conf:5:
> including conf/machine/include/omap3.inc
> DEBUG: BB /scratch/oe/oe-build-daisy/sources/meta-gumstix-community/conf/machine/include/omap3.inc:
> handle(data, include)
> DEBUG: LOAD /scratch/oe/oe-build-daisy/sources/meta-gumstix-community/conf/machine/include/omap3.inc
> 
> Supporting multiple machines in one build present some interesting
> challenges -- what are the best practices in situations like this?
> 
> I guess the good news is I got to try 3.14 on the bb ...

That is interesting indeed. If they felt the need to overwrite the entire 
include file for the SOC, then they should care to keep it updated or set all 
necessary defaults. Otherwise they should have used a more unique name, like 
omap3-gumstix.inc and made necessary customizations in there, keeping the 
original upstream omap3.inc intact and using or not using it from their 
machine configs accordingly. For example, I've dealt with u-boot.inc in a 
similar fashion in meta-ti:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/u-boot/u-boot-ti.inc

-- 
Denys


  reply	other threads:[~2014-07-14 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 13:18 [diasy] omap2plus_defconfig does not include systemd support Cliff Brake
2014-07-11 13:39 ` Maupin, Chase
2014-07-11 15:42 ` Dmytriyenko, Denys
2014-07-11 16:08   ` Dmytriyenko, Denys
2014-07-11 16:24     ` Cliff Brake
2014-07-14 20:26       ` Denys Dmytriyenko [this message]
2014-07-15 15:44         ` Cliff Brake

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=20140714202648.GX15788@edge \
    --to=denys@ti.com \
    --cc=cbrake@bec-systems.com \
    --cc=meta-ti@yoctoproject.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.