Merge lp://qastaging/~vorlon/linaro-image-tools/uboot-refactoring into lp://qastaging/linaro-image-tools/11.11

Proposed by Steve Langasek
Status: Merged
Merged at revision: 100
Proposed branch: lp://qastaging/~vorlon/linaro-image-tools/uboot-refactoring
Merge into: lp://qastaging/linaro-image-tools/11.11
Diff against target: 87 lines (+26/-7)
1 file modified
linaro-media-create (+26/-7)
To merge this branch: bzr merge lp://qastaging/~vorlon/linaro-image-tools/uboot-refactoring
Reviewer Review Type Date Requested Status
Linaro Maintainers Pending
Review via email: mp+35611@code.qastaging.launchpad.net

Description of the change

refactor of u-boot handling in linaro-media-create so that we're sharing code across boards instead of reinventing the wheel for each one. Tested on beagle, but this also affects VE which I can't entirely test, so looking for some more eyeballs on this before pushing.

To post a comment you must log in.
Revision history for this message
James Westby (james-w) wrote :

On Thu, 16 Sep 2010 00:19:50 -0000, Steve Langasek <email address hidden> wrote:
> +
> + if [ -n "$UBOOT_FILE" ] && [ -e "binary/$UBOOT_FILE" ]; then
> + sudo cp -v binary/${UBOOT_FILE} ${DIR}/disk/u-boot.bin
> + fi
> +

Is there a use case for $UBOOT_FILE existing, but not wanted to be copied?

Otherwise this looks ok to me.

Thanks,

James

Revision history for this message
Steve Langasek (vorlon) wrote :

On Thu, Sep 16, 2010 at 12:49:08AM -0000, James Westby wrote:
> On Thu, 16 Sep 2010 00:19:50 -0000, Steve Langasek <email address hidden> wrote:
> > +
> > + if [ -n "$UBOOT_FILE" ] && [ -e "binary/$UBOOT_FILE" ]; then
> > + sudo cp -v binary/${UBOOT_FILE} ${DIR}/disk/u-boot.bin
> > + fi
> > +

> Is there a use case for $UBOOT_FILE existing, but not wanted to be copied?

I don't think so; if you don't want u-boot.bin copied in on that subarch,
don't define it for that subarch?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

Revision history for this message
James Westby (james-w) wrote :

On Thu, 16 Sep 2010 04:58:43 -0000, Steve Langasek <email address hidden> wrote:
> On Thu, Sep 16, 2010 at 12:49:08AM -0000, James Westby wrote:
> > On Thu, 16 Sep 2010 00:19:50 -0000, Steve Langasek <email address hidden> wrote:
> > > +
> > > + if [ -n "$UBOOT_FILE" ] && [ -e "binary/$UBOOT_FILE" ]; then
> > > + sudo cp -v binary/${UBOOT_FILE} ${DIR}/disk/u-boot.bin
> > > + fi
> > > +
>
> > Is there a use case for $UBOOT_FILE existing, but not wanted to be copied?
>
> I don't think so; if you don't want u-boot.bin copied in on that subarch,
> don't define it for that subarch?

Sounds sensible to me.

The current way just means that we may create images without u-boot if
the file isn't found for some reason. I would expect it to fail instead.

Thanks,

James

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches