All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ODROID-C1 support
Date: Thu, 21 May 2015 14:26:33 -0400	[thread overview]
Message-ID: <555E2359.3080509@gmail.com> (raw)
In-Reply-To: <5548E485.6080505@gmail.com>

Hi Christian,

On 05/05/15 11:40, Christian Ege wrote:
> I've created a BSP Layer for the ODROID-C1 and other Amlogic based
> devices like the Wetek.Play
>
> https://github.com/linux-meson/meta-amlogic

Thanks! I've been playing with your layer. For the most part it's going
well. I've noticed a small glitch, however, and I'm not 100% sure how to
fix it (otherwise I would have just sent you a github pull request).

If I have your layer added to the BBLAYERS mix but I'm _not_ building
for "odroidc1" (or "wetekplay", I assume) then I get an error because
the build system can't find the amlsetfb.sh file. You have two
"amlsetfb.sh" files, one for the odroidc1 and one for the wetekplay
which you've added to recipes-core/initscripts/odroidc1 and
recipes-core/initscripts/wetekplay. If the MACHINE is odroidc1 then the
recipes-core/initscripts/odroidc1/amsetfb.sh file is found, otherwise it
is not.

I can work around this issue by adding a MACHINE-specific override to
your initscripts_1.%.bbappend:

-SRC_URI_append = " file://amlsetfb.sh \
+SRC_URI_append_odroidc1 = " file://amlsetfb.sh \

but I'm guessing another override would be required for the wetekplay as
well.

Why would someone include your layer and not build for odroidc1 or
wetekplay? Sometimes that's what people do ;-) (look at Angstrom, for
example). Besides, a BSP layer should be able to play nicely with other
layers even when its machines aren't being used :-)


  parent reply	other threads:[~2015-05-21 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 15:40 ODROID-C1 support Christian Ege
2015-05-08 13:44 ` Trevor Woerner
2015-05-21 18:26 ` Trevor Woerner [this message]
2015-05-21 20:55   ` Christian Ege
2015-05-21 21:18   ` Khem Raj
2015-05-22 23:15     ` Trevor Woerner
2015-05-23  0:30       ` 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=555E2359.3080509@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-devel@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.