From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mips: Allow overriding start.S in SPL
Date: Thu, 26 May 2016 01:25:00 +0200 [thread overview]
Message-ID: <5746344C.6040201@gmail.com> (raw)
In-Reply-To: <1464135462-6876-1-git-send-email-marex@denx.de>
Am 25.05.2016 um 02:17 schrieb Marek Vasut:
> Certain chips, like the JZ47xx, have extreme size constraints on the
> SPL size and require custom start.S . Allow overriding the start.S
> the same way ARM MXS does it.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
> Cc: Paul Burton <paul.burton@imgtec.com>
> ---
> arch/mips/Makefile | 6 ++++++
> 1 file changed, 6 insertions(+)
>
applied to u-boot-mips, thanks.
--
- Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160526/dbf1fdf8/attachment.sig>
prev parent reply other threads:[~2016-05-25 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 0:17 [U-Boot] [PATCH] mips: Allow overriding start.S in SPL Marek Vasut
2016-05-25 23:25 ` Daniel Schwierzeck [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=5746344C.6040201@gmail.com \
--to=daniel.schwierzeck@gmail.com \
--cc=u-boot@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox