From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 0/7] Add support for NVIDIA Tegra30 SoC
Date: Tue, 11 Dec 2012 17:09:45 -0800 [thread overview]
Message-ID: <20121212010945.GD25496@badger> (raw)
In-Reply-To: <1355268858-7868-1-git-send-email-twarren@nvidia.com>
On Tue, Dec 11, 2012 at 03:34:11PM -0800, Tom Warren wrote:
> This patch series adds basic (boot to cmd prompt) support for Tegra30.
> This is based on the Tegra20 SPL, which initializes the AVP (ARM7TDMI)
> boot proc) first, then control is transferred to the CPU (A9 quad cluster).
> It is based on current u-boot-tegra/next. Some Tegra20 files were
I wasn't able to get these to apply cleanly to u-boot-tegra/next. It
failed on the first patch:
$ git am ~/twarren
Applying: Tegra30: Add arch-tegra30 include files
error: patch failed: arch/arm/include/asm/arch-tegra/clk_rst.h:37
error: arch/arm/include/asm/arch-tegra/clk_rst.h: patch does not apply
error: patch failed: arch/arm/include/asm/arch-tegra/clock.h:136
error: arch/arm/include/asm/arch-tegra/clock.h: patch does not apply
error: patch failed: arch/arm/include/asm/arch-tegra/tegra.h:72
error: arch/arm/include/asm/arch-tegra/tegra.h: patch does not apply
error: patch failed: arch/arm/include/asm/arch-tegra20/funcmux.h:62
error: arch/arm/include/asm/arch-tegra20/funcmux.h: patch does not apply
error: patch failed: arch/arm/include/asm/arch-tegra20/gp_padctrl.h:61
error: arch/arm/include/asm/arch-tegra20/gp_padctrl.h: patch does not apply
Patch failed at 0001 Tegra30: Add arch-tegra30 include files
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
--
nvpublic
next prev parent reply other threads:[~2012-12-12 1:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 23:34 [U-Boot] [PATCH V3 0/7] Add support for NVIDIA Tegra30 SoC Tom Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 1/7] Tegra30: Add arch-tegra30 include files Tom Warren
2012-12-12 0:36 ` Stephen Warren
2012-12-12 16:23 ` Tom Warren
2012-12-12 22:02 ` Stephen Warren
2012-12-12 23:06 ` Tom Warren
2012-12-12 14:55 ` Simon Glass
2012-12-11 23:34 ` [U-Boot] [PATCH V3 2/7] Tegra30: Add AVP (arm720t) files Tom Warren
2012-12-12 0:40 ` Stephen Warren
2012-12-12 16:24 ` Tom Warren
2012-12-12 14:58 ` Simon Glass
2012-12-11 23:34 ` [U-Boot] [PATCH V3 3/7] Tegra30: Add CPU (armv7) files Tom Warren
2012-12-12 0:41 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 4/7] Tegra30: Add common CPU (shared) files Tom Warren
2012-12-12 0:45 ` Allen Martin
2012-12-12 16:14 ` Tom Warren
2012-12-12 22:06 ` Stephen Warren
2012-12-12 23:07 ` Tom Warren
2012-12-12 22:09 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 5/7] Tegra30: Cardhu: Add DT files Tom Warren
2012-12-12 22:10 ` Stephen Warren
2012-12-12 23:11 ` Tom Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 6/7] Tegra30: Add generic Tegra30 build support Tom Warren
2012-12-12 22:13 ` Stephen Warren
2012-12-11 23:34 ` [U-Boot] [PATCH V3 7/7] Tegra30: Add/enable Cardhu build (T30 reference board) Tom Warren
2012-12-12 22:21 ` Stephen Warren
2012-12-12 1:09 ` Allen Martin [this message]
2012-12-12 2:47 ` [U-Boot] [PATCH V3 0/7] Add support for NVIDIA Tegra30 SoC Allen Martin
2012-12-12 3:05 ` Allen Martin
2012-12-12 22:40 ` Simon Glass
2012-12-12 23:12 ` Tom Warren
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=20121212010945.GD25496@badger \
--to=amartin@nvidia.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 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.