From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Denis OSTERLAND <denis.osterland@diehl.com>,
Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 2/2] u-boot: Allow generation of boot script
Date: Fri, 12 Apr 2019 16:17:30 +0200 [thread overview]
Message-ID: <9909219.cSBnJ8OjsF@ada> (raw)
In-Reply-To: <20190412140956.z3hbjx77h2pzifqy@pengutronix.de>
Hello,
Am Freitag, 12. April 2019, 16:09:56 CEST schrieb Michael Olbrich:
> On Fri, Apr 12, 2019 at 03:17:33PM +0200, Alexander Dahl wrote:
> > Am Freitag, 12. April 2019, 09:49:18 CEST schrieb Michael Olbrich:
> > > On Thu, Apr 11, 2019 at 01:09:37PM +0200, Alexander Dahl wrote:
> > > > #
> > > > ---------------------------------------------------------------------
> > > > ---
> > > > ---->
> > > >
> > > > +# Compile
> > > > +#
> > > > ----------------------------------------------------------------------
> > > > ---
> > > > --- +
> > > > +$(STATEDIR)/u-boot.compile:
> > > > + @$(call targetinfo)
> > > > + @$(call world/compile, U_BOOT)
> > > > +ifdef PTXCONF_U_BOOT_BOOT_SCRIPT
> > > > + @$(U_BOOT_DIR)/tools/mkimage -T script -C none \
> > > > + -d $(U_BOOT_BOOT_SCRIPT_TXT) \
> > > > + $(U_BOOT_DIR)/uboot.scr
> > >
> > > I don't mind the name, but you could use
> > > '$(notdir $(U_BOOT_BOOT_SCRIPT_TXT))' here and below.
> >
> > Not sure what you mean here. 'mkimage' expects the [image data file] after
> > option '-d', which is the input file not just a name. And what is 'below'
> > supposed to mean here?
>
> Sorry, I mixed up the variable names. I meant:
>
> @$(U_BOOT_DIR)/tools/mkimage -T script -C none \
> -d $(U_BOOT_BOOT_SCRIPT_TXT) \
> $(U_BOOT_DIR)/$(notdir $(U_BOOT_BOOT_SCRIPT_BIN))
>
> As a way to handle Denis' complaint about the same suffix for both files.
> I don't really care either way. I don't know what the naming conventions
> are for this.
Ah I had overlooked that comment. It's not that bad, this image goes to build-
target and is copied over in targetinstall as a final step. But if being
pedantic, it should be called e.g. 'boot.scr.uimg' in build-target, too.
Okay, I will cover that in v2 next week. Thanks for your feedback.
Have a nice weekend
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-04-12 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 11:09 [ptxdist] [PATCH 0/2] u-boot: boot script and series option Alexander Dahl
2019-04-11 11:09 ` [ptxdist] [PATCH 1/2] Revert "readd _SERIES option for u-boot and add it for at91bootstrap (partially reverts dac31c4)" Alexander Dahl
2019-04-11 11:09 ` [ptxdist] [PATCH 2/2] u-boot: Allow generation of boot script Alexander Dahl
2019-04-11 13:05 ` Denis OSTERLAND
2019-04-12 7:49 ` Michael Olbrich
2019-04-12 13:17 ` Alexander Dahl
2019-04-12 14:09 ` Michael Olbrich
2019-04-12 14:17 ` Alexander Dahl [this message]
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=9909219.cSBnJ8OjsF@ada \
--to=ada@thorsis.com \
--cc=denis.osterland@diehl.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox