All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] omap-u-boot-utils: add new package
Date: Wed, 14 Sep 2011 10:58:01 +0200	[thread overview]
Message-ID: <4E706C99.1090206@lucaceresoli.net> (raw)
In-Reply-To: <20110913194446.0ebab8c5@skate>

Thomas,
thanks for the review.

Thomas Petazzoni wrote:
> Le Tue, 13 Sep 2011 19:19:32 +0200,
> Luca Ceresoli<luca@lucaceresoli.net>  a ?crit :
>
>> +++ b/boot/omap-u-boot-utils/Config.in
>> @@ -0,0 +1,7 @@
>> +config BR2_PACKAGE_HOST_OMAP_U_BOOT_UTILS
>> +	bool "omap-u-boot-utils"
>> +	help
>> +	  U-Boot Utilities for Texas Instrument's OMAP platforms.
>> +	  Say Y if you want these utilities on the development host.
>> +
>> +	  https://github.com/nmenon/omap-u-boot-utils
>
> This is a pure host package, so it shouldn't be present in any
> Config.in file. See package/fakeroot as an example.
>
> And even if it also was a target package, the Config.in should be in
> the package directory, not in boot/.

If I understand correctly your point, you would make omap-u-boot-utils
automatically compile if BR2_TARGET_UBOOT_OMAP_IFT (patch 2/2) is on,
without any user-visible option.

But this would reduce flexibility.

To understand why, consider this package is a set of utilities, loosely
related to each other.

gpsign is absolutely OMAP-specific, and it's what I use in patch 2/2 in
order to build a .ift image from a .bin image.

OTOH, ucmd "sends a command and expects a provided matching response
from target", and is aimed at creating automated scripts to interact
with a commandline program over a serial line. This can be used in any
architecture. I have board-specific scripts that use it to write
bootloader + kernel + rootfs onto a new (or bricked) board from files in
output/images.

So, while omap-u-boot-utils is a requirement for building a signed
image, I think it should be also available as a user option in
menuconfig.
I'm not sure boot/omap-u-boot-utils/Config.in is the correct place
anyway, I'm open to suggestions on a better location.


Oh, and to be complete, this might be a target package too; I did not
implement that because cross-compilation is a bit tricky and the use
case is possibly not interesting to anybody.

>
>> +OMAP_U_BOOT_UTILS_VERSION = d086cb5c0
>> +OMAP_U_BOOT_UTILS_SOURCE = omap-u-boot-utils-$(OMAP_U_BOOT_UTILS_VERSION).tar.gz
>
> xxx_SOURCE is useless with the git download method.

Right. Will fix.

>
>> +OMAP_U_BOOT_UTILS_TARGETS = gpsign pserial tagger ucmd ukermit
>
> Used only once, just hardcode.

Well, ok. Will do.

Luca

  reply	other threads:[~2011-09-14  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 17:19 [Buildroot] [PATCH 1/2] omap-u-boot-utils: add new package Luca Ceresoli
2011-09-13 17:19 ` [Buildroot] [PATCH 2/2] u-boot: build signed image for OMAP processors Luca Ceresoli
2011-09-13 18:14   ` Gustavo Zacarias
2011-09-14  8:39     ` Luca Ceresoli
2011-09-13 17:44 ` [Buildroot] [PATCH 1/2] omap-u-boot-utils: add new package Thomas Petazzoni
2011-09-14  8:58   ` Luca Ceresoli [this message]
2011-09-19 14:53 ` [Buildroot] [PATCH v2 " Luca Ceresoli
2011-09-19 14:53   ` [Buildroot] [PATCH v2 2/2] u-boot: build signed image for OMAP processors Luca Ceresoli
2011-09-19 20:44   ` [Buildroot] [PATCH v2 1/2] omap-u-boot-utils: add new package Thomas Petazzoni
2011-09-21 13:00     ` Luca Ceresoli

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=4E706C99.1090206@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /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.