All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: u-boot precompiled ?
Date: Fri, 05 Dec 2014 07:22:07 -0700	[thread overview]
Message-ID: <5481BF8F.4030403@mlbassoc.com> (raw)
In-Reply-To: <4009F04F5925CD4C95FBD9BE756381FE02848F2A75@MSSRVS5.atlas.de>

On 2014-12-05 05:48, Matthias.Heise@atlas-elektronik.com wrote:
> Hello Matt,
>
> thanks very much for your reply, I was able to create a simple patch changing an u-boot setting as test and “bbappended” it. I just didn’t believe before that the various u-boot
> settings are “hard-coded” but they obviously are in the “<board>.h”, so patching it seems to be the only way for changing settings from within yocto, right?

What U-Boot settings are you asking about?

> *Von:*Matt Schuckmann [mailto:Matt.Schuckmann@planar.com]
> *Gesendet:* Donnerstag, 4. Dezember 2014 18:31
> *An:* Heise, Matthias; yocto@yoctoproject.org
> *Betreff:* RE: u-boot precompiled ?
>
> Mat,
>
> I’m fairly new to OpenEmbedded (4 months now and I still feel like a noobi but I’m trying to give back while the pain is still fresh in my mind)
>
> For something like u-boot it kind of depends on what your changing. If you need to change the u-boot code and the changes are small then typically you’d create a patch f for your
> changes and then make them part of a .bbappend in your layer for the recipe. There are examples on the net for how to create a .bbappend and reference the patch file.
>
> Generally your .bbappend can be as simple as:
>
> FILESEXTRAPATHS_prepend = “:${THISDIR}/files”
>
> SRC_URI += “files://xyzzy.patch”
>
> Where your patches are in subdirectory of your recipe directory.
>
> Remember that generally recipes are about how to obtain the code, build it and package it for distribution, you can do recipes that deal with a pre-built binary but that is
> generally not the case.
>
> Hope this helps,
>
> Matt S.
>
> *From:*yocto-bounces@yoctoproject.org <mailto:yocto-bounces@yoctoproject.org> [mailto:yocto-bounces@yoctoproject.org] *On Behalf Of *Matthias.Heise@atlas-elektronik.com
> <mailto:Matthias.Heise@atlas-elektronik.com>
> *Sent:* Thursday, December 04, 2014 1:49 AM
> *To:* yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> *Subject:* Re: [yocto] u-boot precompiled ?
>
> Even if this is a stupid question a little advise would be nice … like “don’t ask so stupid questions, go read this and that” or something… no time ? Should I rather unsubscribe
> from this list until I’m an expert?
>
> *Von:*Heise, Matthias
> *Gesendet:* Mittwoch, 3. Dezember 2014 15:15
> *An:* 'yocto@yoctoproject.org'
> *Betreff:* u-boot precompiled ?
>
> Hi all,
>
> I’m still trying to find out basic things about getting a system up and running. This question is about U-Boot, is it right that for example for my wandboard a pre-compiled *.imx
> is just downloaded ?
>
> So if I want to make settings to U-Boot I make them directly in the source, compile it and re-direct in a recipe to take that new file as bootloader ? Or can I make the settings
> within a recipe and I just didn’t find the spot ?
>
> Thanks for your time,
>
> Regards
>
> Mat
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2014-12-05 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 14:15 u-boot precompiled ? Matthias.Heise
2014-12-04  9:49 ` Matthias.Heise
2014-12-04 17:30   ` Matt Schuckmann
2014-12-05 12:48     ` Matthias.Heise
2014-12-05 14:22       ` Gary Thomas [this message]
2014-12-08  8:32         ` Matthias.Heise

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=5481BF8F.4030403@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@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.