From: Geoff Levand <geoffrey.levand@am•sony.com>
To: David Woodhouse <dwmw2@infradead•org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PPC BOOT] Create otheros.bld next to specified output file, not in $object directory.
Date: Sun, 02 Dec 2007 19:33:50 -0800 [thread overview]
Message-ID: <4753791E.6020703@am.sony.com> (raw)
In-Reply-To: <1196650083.13978.113.camel@pmac.infradead.org>
David Woodhouse wrote:
> The bootwrapper script currently generates an 'otheros.bld' file in
> addition to the file specified by the -o option, when asked to build a
> wrapper for PS3.
>
> It should do that in the same directory as the output, not the directory
> where the wrapper objects are kept (which might potentially not be
> writable when the script runs).
Seems reasonable for installs from read-only media.
> Arguably, the 'otheros.bld' ought to be created with the filename
> specified as the -o argument. But that's a more intrusive change.
Yes, I think it makes sense. ps3-flash-util can handle any file
name, so there is no real reason to have it named otheros.bld.
> Signed-off-by: David Woodhouse <dwmw2@infradead•org>
Acked-by: Geoff Levand <geoffrey.levand@am•sony.com>
prev parent reply other threads:[~2007-12-03 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 2:48 [PPC BOOT] Create otheros.bld next to specified output file, not in $object directory David Woodhouse
2007-12-03 2:49 ` [PPC BOOT] Find device-tree source file in default directory David Woodhouse
2007-12-03 2:52 ` [PPC BOOT] Allow for bootwrapper utilities being in different directory to objects David Woodhouse
2007-12-03 2:56 ` [PPC BOOT] 'make bootwrapper_install' David Woodhouse
2007-12-03 15:08 ` [PPC BOOT] Find device-tree source file in default directory Scott Wood
2007-12-03 15:13 ` David Woodhouse
2007-12-03 3:33 ` Geoff Levand [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=4753791E.6020703@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=dwmw2@infradead$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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