linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [U-Boot] zImage and raw ramdisk support -- test
Date: Fri, 30 Mar 2012 22:24:20 +0200	[thread overview]
Message-ID: <201203302224.20196.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAOCHtYiewpJ6PERFP_O-0gXkkrQte1kL3m4za9=9ZaNBMgyqLg@mail.gmail.com>

Dear Robert Nelson,

> On Fri, Mar 30, 2012 at 10:38 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > Guys,
> > 
> > I need final test on as much platforms as possible. Can you please run
> > these two following patches and tell me if they work with zImage and raw
> > ramdisk for you?
> > 
> > http://patchwork.ozlabs.org/patch/146848/
> > http://patchwork.ozlabs.org/patch/147440/
> > 
> > I can't promise they will make it to this release (I've been pestering WD
> > pretty thoroughly (sorry about that), though I'm starting to be unhappy
> > to merge this stuff at the verge of release myself).
> 
> Hi Marek,
> 
> These work great on my omap3 Beagle xM C / omap4 Panda, using a zImage
> and initramfs..
> 
> Just added the two appropriate board configs, to enable it..
> #define CONFIG_CMD_BOOTZ
> #define CONFIG_SUPPORT_RAW_INITRD
> 
> and used todays u-boot git head:
> http://git.denx.de/?p=u-boot.git;a=commit;h=7cb30b13f12077c7eec8ce2419cd96c
> d65ace8e2

And it makes u-boot about 20% cooler, doesn't it ;-)

Thanks a lot for your testing!

> Tested-by: Robert Nelson <robertcnelson@gmail.com>
> 
> Regards,

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-30 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 15:38 zImage and raw ramdisk support -- test Marek Vasut
2012-03-30 19:30 ` [U-Boot] " Robert Nelson
2012-03-30 20:24   ` Marek Vasut [this message]
2012-03-30 21:38     ` Wolfgang Denk

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=201203302224.20196.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).