All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matteo Fortini <matteo.fortini@mta.it>
To: Wolfgang Denk <wd@denx.de>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Booting uncompressed kernel image
Date: Tue, 27 Jan 2009 11:03:52 +0100	[thread overview]
Message-ID: <497EDC08.4080204@mta.it> (raw)
In-Reply-To: <20090126223645.791B7832E416@gemini.denx.de>

You're right,
to be precise, the --no-gzip option was given to the wrapper script, the 
option I gave to mkimage was -C none.

The change in the wrapper script was adding:
case "$platform" in
ubootraw)
    rm -f "$ofile"
    mkimage -A ppc -O linux -T kernel -C none -a 00000000 -e 00000000 \
    $uboot_version -d "$vmz" "$ofile"
    if [ -z "$cacheit" ]; then
    rm -f "$vmz"
    fi
    exit 0
    ;;
esac


and I called wrapper as
./arch/powerpc/boot/wrapper  -c -o arch/powerpc/boot/uImage -p ubootraw 
-C "powerpc-e300c3-linux-gnu-" --no-gzip vmlinux

Anyway, I'll check the solution given by Luotao, thanks!

Regards,
Matteo

Wolfgang Denk ha scritto:
> Dear Matteo Fortini,
>
> In message <497D9BC8.0@mta.it> you wrote:
>   
>> I built an uncompressed uImage using mkimage --no-gzip -C none in the 
>> wrapper scripts.
>>     
>
> Hm... you must be using a funny version of mkimage, then. The cod in
> mainline will bail out on "--no-gzip".
>
> Best regards,
>
> Wolfgang Denk
>
>   

  reply	other threads:[~2009-01-27 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 11:17 Booting uncompressed kernel image Matteo Fortini
2009-01-26 22:36 ` Wolfgang Denk
2009-01-27 10:03   ` Matteo Fortini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-26 11:30 Matteo Fortini
2009-01-26 15:23 ` Luotao Fu

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=497EDC08.4080204@mta.it \
    --to=matteo.fortini@mta.it \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wd@denx.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 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.