All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: update to 2013.07
Date: Mon, 26 Aug 2013 16:48:36 -0500	[thread overview]
Message-ID: <521BCD34.8090003@pabigot.com> (raw)
In-Reply-To: <521B9698.7030803@linux.intel.com>

I can confirm this also works with the Gumstix Overo in a layer bbappend 
that used SRC_URI_append_overo for additional patches.  Thanks to you 
both for getting it merged.

I did come up with a question, though.  The recipe uses:

   PV = "v2013.07+git${SRCPV}"

which creates an informative but ugly ${BPN}.  I'd like to use something 
like:

   FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"

in the bbappend to simplify updates, but I don't want to have a 
directory named u-boot-v2013.07+gitAUTOINC+62c175fbb8.  For linux-yocto, 
this is solved through introduction of ${LINUX_VERSION} allowing 
${PN}-${LINUX_VERSION}.

Is there reason to create a parallel UBOOT_VERSION?

Is there reason to have some way to access the default ${PV} inferred 
from the recipe name before the base recipe overrode it? (Is there 
already some way to get that value?)

Is there a better approach than bbappend-in-layer that I should use for 
adding patches required for a specific u-boot machine?

Peter

On 08/26/2013 12:55 PM, Saul Wold wrote:
> On 08/23/2013 09:57 AM, Laszlo Papp wrote:
>> Any update? It would be nice not to miss the freeze ... ;-)
>>
> This has been merged, and I was informed by the QA team that it works 
> correctly for the mpc8315e-rdb and beagleboard, but NOT the 
> beagleboard XM.



  reply	other threads:[~2013-08-26 21:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  9:48 [PATCH] u-boot: update to 2013.07 Laszlo Papp
2013-08-23 16:57 ` Laszlo Papp
2013-08-23 21:56   ` Saul Wold
2013-08-24  4:31     ` Saul Wold
2013-08-26 17:55   ` Saul Wold
2013-08-26 21:48     ` Peter A. Bigot [this message]
2013-08-26 21:55       ` Laszlo Papp
2013-08-26 22:03       ` Bruce Ashfield
2013-08-27 10:45     ` Laszlo Papp
2013-08-27 19:57 ` Randy MacLeod
2013-08-27 20:03   ` Laszlo Papp
2013-08-27 20:08   ` Martin Jansa
2013-08-27 23:29     ` Richard Purdie
2013-08-28  3:50       ` Randy MacLeod
2013-08-29  7:16         ` jhuang0
2013-08-28 16:00   ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2013-08-26 18:06 Laszlo Papp
2013-08-22 20:36 Laszlo Papp
2013-08-22 21:14 ` Laszlo Papp
2013-08-23  7:26   ` Laszlo Papp
2013-08-15  4:25 Laszlo Papp
2013-08-15  9:16 ` Jack Mitchell
2013-08-15 10:36   ` Laszlo Papp
2013-08-03  9:17 Laszlo Papp
2013-08-03 17:53 ` Otavio Salvador
2013-08-03 18:12   ` Laszlo Papp
2013-08-03 20:00     ` Saul Wold
2013-08-03 20:05       ` Otavio Salvador
2013-08-05  4:09 ` Saul Wold
2013-08-05 16:49 ` Saul Wold
     [not found]   ` <CAOMwXhN_0SgvFEY1ai9ZntkC-zPCBgbUaQNjqPeoNe931Xr_8w@mail.gmail.com>
     [not found]     ` <CAOMwXhNYeqM6m_R0eTpqHjK-E9d6qmqQw7aGeOJEEqOeByw29A@mail.gmail.com>
2013-08-06 14:05       ` Saul Wold
2013-07-31 13:16 Laszlo Papp
2013-07-31 13:24 ` Burton, Ross
2013-07-31 15:13   ` Laszlo Papp
2013-07-31 13:14 Laszlo Papp

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=521BCD34.8090003@pabigot.com \
    --to=pab@pabigot.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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.