From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 6/6] T210: Add support for 64-bit T210-based P2571 board
Date: Wed, 22 Jul 2015 12:04:37 -0600 [thread overview]
Message-ID: <55AFDB35.8080901@wwwdotorg.org> (raw)
In-Reply-To: <1437421844-5157-7-git-send-email-twarren@nvidia.com>
On 07/20/2015 01:50 PM, Tom Warren wrote:
> Based on Venice2, incorporates Stephen Warren's
> latest P2571 pinmux table.
>
> With Thierry Reding's 64-bit build fixes, this
> will build and and boot in 64-bit on my P2571
> (when used with a 32-bit AVP loader).
> diff --git a/include/configs/venice2.h b/include/configs/p2571.h
> /* USB Host support */
> #define CONFIG_USB_EHCI
> #define CONFIG_USB_EHCI_TEGRA
> -#define CONFIG_USB_MAX_CONTROLLER_COUNT 2
> +#define CONFIG_USB_MAX_CONTROLLER_COUNT 1
Why's that?
> -/* USB networking support */
> -#define CONFIG_USB_HOST_ETHER
> -#define CONFIG_USB_ETHER_ASIX
> -
> -/* General networking support */
> -#define CONFIG_CMD_DHCP
I assume that's to solve some compile issue? If so, a FIXME/TODO comment
(like you added for tegra-common-usb-gadget.h) would be better, so it's
obvious we need to go back and re-enable it.
> +#if defined(CONFIG_ARM64)
> +#define COUNTER_FREQUENCY 12000000
> +#define CPU_RELEASE_ADDR 0x80000000
> +#endif
CONFIG_ARM64 is always true now.
According to the schematics, the crystal frequency is 38.4MHz.
Where did the value of CPU_RELEASE_ADDR come from? It's odd that there
are 4 CPUs but only 1 release address.
> diff --git a/include/configs/tegra124-common.h b/include/configs/tegra210-common.h
> -#define CONFIG_SYS_TEXT_BASE 0x80110000
> +#define CONFIG_SYS_TEXT_BASE 0x8010E000
It'd be best to keep that consistent with earlier chips.
next prev parent reply other threads:[~2015-07-22 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 19:50 [U-Boot] [PATCH V2 0/6] Tegra210/P2571 initial support Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 1/6] Tegra210: Fix 64-bit build warning about save_boot_params_ret() Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 2/6] Tegra: Rework KConfig options to allow 64-bit builds (T210) Tom Warren
2015-07-22 17:40 ` Stephen Warren
2015-07-22 20:05 ` Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 3/6] ARM: Tegra210: Add SoC code/include files for T210 Tom Warren
2015-07-22 17:44 ` Stephen Warren
2015-07-23 15:34 ` Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 4/6] ARM: Tegra210: Add support to common Tegra source/config files Tom Warren
2015-07-22 17:52 ` Stephen Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 5/6] P2571: dts: Add DT files for Tegra210/P2571 board Tom Warren
2015-07-22 17:57 ` Stephen Warren
2015-07-23 17:41 ` Tom Warren
2015-07-22 18:16 ` Stephen Warren
2015-07-23 17:44 ` Tom Warren
2015-07-23 17:59 ` Stephen Warren
2015-07-23 19:06 ` Tom Warren
2015-07-23 19:30 ` Stephen Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 6/6] T210: Add support for 64-bit T210-based P2571 board Tom Warren
2015-07-22 18:04 ` Stephen Warren [this message]
2015-07-23 23:17 ` Tom Warren
2015-07-22 18:10 ` [U-Boot] [PATCH V2 0/6] Tegra210/P2571 initial support Stephen Warren
2015-07-22 20:35 ` Stephen Warren
2015-07-22 21:07 ` 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=55AFDB35.8080901@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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