From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] u-boot: add Marvell u-boot.kwb support
Date: Mon, 26 Jul 2010 22:31:26 +0200 [thread overview]
Message-ID: <4C4DF09E.502@gmx.net> (raw)
In-Reply-To: <20100726141846.1699E8262B@busybox.osuosl.org>
Am 26.07.2010 16:14, schrieb Peter Korsgaard:
>
> commit: http://git.buildroot.net/buildroot/commit/?id=3cd5174ed796400a9566c0ea52f3551cba52bfe0
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> Marvell boards like the sheevaplug needs a special .kwb image format,
> so add an option for it similar to how we handle zImage/uImage/..
> for the kernel.
>
Just for documentation if someone searches the mailingarchive:
I run a plain vanilla u-boot with a minor patch in bin-format on my
seagate dockstar (sheevaplug with less memory). But this is chainloaded
by the proprietary u-boot. So at least for this configuration you are
not forced to use the .kwb format.
@Peter:
Please note my patch for applying patches to u-boot. The current git
tree includes a typo. I corrected it and submitted the patch more than
once to the mailinglist (see attachement).
The solution is rather forward and the patch is tested (only two
modified lines).
Kind regards,
Marcus
-------------- next part --------------
An embedded message was scrubbed...
From: Ossy <ossy1980@gmx.net>
Subject: [Buildroot] [PATCH] apply custom patches correctly to u-boot
Date: Wed, 07 Jul 2010 22:55:55 +0200
Size: 6342
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100726/6fc01c14/attachment-0001.mht>
next prev parent reply other threads:[~2010-07-26 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:14 [Buildroot] [git commit master 1/1] u-boot: add Marvell u-boot.kwb support Peter Korsgaard
2010-07-26 20:31 ` Ossy [this message]
2010-07-26 20:47 ` Peter Korsgaard
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=4C4DF09E.502@gmx.net \
--to=ossy1980@gmx.net \
--cc=buildroot@busybox.net \
/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