Tegra: T30: Beaver board support.
PATCH 1/1 Tegra: T30: Beaver board support.
Beaver is a Tegra30 board that is nearly 100% compatible w/Cardhu. Add a Beaver build so it can begin to be differentiated, if need be.
--- board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++ board/nvidia/dts/tegra30-beaver.dts | 66 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + 3 files changed, 105 insertions(+) create mode 100644 board/nvidia/beaver/Makefile create mode 100644 board/nvidia/dts/tegra30-beaver.dts
board/nvidia/beaver/Makefile new file +38 -0
@@ -0,0 +1,38 @@ +# +# Copyright (c) 2010-2013, NVIDIA CORPORATION. All rights reserved. +# +# This program is free software; you can redistribute it and/or modify it +# under the terms and conditions of the GNU General Public License, +# version 2, as published by the Free Software Foundation. +# +# This program is distributed in the hope it will be useful, but WITHOUT +# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for +# more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. +# + +include $(TOPDIR)/config.mk + +$(shell mkdir -p $(obj)../cardhu) + +LIB = $(obj)lib$(BOARD).o + +COBJS = ../cardhu/cardhu.o + +SRCS := $(COBJS:.o=.c) +OBJS := $(addprefix $(obj),$(COBJS)) + +$(LIB): $(obj).depend $(OBJS) + $(call cmd_link_o_target, $(OBJS)) + +######################################################################### + +# defines $(obj).depend target +include $(SRCTREE)/rules.mk + +sinclude $(obj).depend + +#########################################################################
board/nvidia/dts/tegra30-beaver.dts new file +66 -0
66 lines not on this page · raw message
boards.cfg +1 -0
@@ -310,6 +310,7 @@ seaboard arm armv7:arm720t seaboard nvidia ventana arm armv7:arm720t ventana nvidia tegra20 whistler arm armv7:arm720t whistler nvidia tegra20 cardhu arm armv7:arm720t cardhu nvidia tegra30 +beaver arm armv7:arm720t beaver nvidia tegra30 dalmore arm armv7:arm720t dalmore nvidia tegra114 colibri_t20_iris arm armv7:arm720t colibri_t20_iris toradex tegra20 u8500_href arm armv7 u8500 st-ericsson u8500
Signature · 1 line
1.8.1.5
PATCH 1/1 Tegra: T30: Beaver board support.
Quoted 8 lines · Tom Warren
Beaver is a Tegra30 board that is nearly 100% compatible w/Cardhu. Add a Beaver build so it can begin to be differentiated, if need be.
Signed-off-by Tom Warren <[email protected]>--- board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++ board/nvidia/dts/tegra30-beaver.dts | 66 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 +
OK, I assume cardhu and beaver dts files differ, right? If so, maybe we can find a smaller way to just say we have N boards that use a different dts, but that's it?
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130412/04c715b0/attachment.pgp>
PATCH 1/1 Tegra: T30: Beaver board support.
Quoted 6 lines · Tom Rini
Quoted 4 lines · Tom Warren
Beaver is a Tegra30 board that is nearly 100% compatible w/Cardhu. Add a Beaver build so it can begin to be differentiated, if need be.
Quoted 8 lines
Quoted 4 lines
Signed-off-by Tom Warren <[email protected]> ---board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++
board/nvidia/dts/tegra30-beaver.dts| 66 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 +OK, I assume cardhu and beaver dts files differ, right? If so, maybe we can find a smaller way to just say we have N boards that use a different dts, but that's it?
I think you can do that just be modifying boards.cfg; n lines with the same content except for the name in the first column, e.g.:
Quoted 2 lines
snow arm armv7 smdk5250 samsung exynos smdk5250 arm armv7 smdk5250 samsung exynos
You can also add an extra column with options if needed, although I imagine the makefiles can see the value of the first column to e.g. select different .dts files?
Perhaps we should do the same for Seaboard/Ventana too.
PATCH 1/1 Tegra: T30: Beaver board support.
In reply to Tom RiniQuoted 9 lines · Tom Rini
Quoted 7 lines · Tom Warren
Beaver is a Tegra30 board that is nearly 100% compatible w/Cardhu. Add a Beaver build so it can begin to be differentiated, if need be.
Signed-off-by Tom Warren <[email protected]>--- board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++ board/nvidia/dts/tegra30-beaver.dts | 66
Quoted 8 lines
+++++++++++++++++++++++++++++++++++++
Quoted 1 line
boards.cfg | 1 +OK, I assume cardhu and beaver dts files differ, right? If so, maybe we can find a smaller way to just say we have N boards that use a different dts, but that's it?
Right now, they only differ in the 'model' and 'compatible' fields
(because of the name change), and max memory (Beaver has more).
At some point, it may be more than just a DTS difference, though.
Tom
Quoted 1 line
PATCH 1/1 Tegra: T30: Beaver board support.
Quoted 14 lines · Tom Warren
Quoted 12 lines · Tom Rini
Quoted 7 lines · Tom Warren
Beaver is a Tegra30 board that is nearly 100% compatible w/Cardhu. Add a Beaver build so it can begin to be differentiated, if need be.
Signed-off-by Tom Warren <[email protected]>--- board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++ board/nvidia/dts/tegra30-beaver.dts | 66+++++++++++++++++++++++++++++++++++++
Quoted 1 line
boards.cfg | 1 +
Quoted 8 lines
Quoted 5 lines
OK, I assume cardhu and beaver dts files differ, right? If so, maybe we can find a smaller way to just say we have N boards that use a different dts, but that's it?
Right now, they only differ in the 'model' and 'compatible' fields
(because of the name change), and max memory (Beaver has more).
At some point, it may be more than just a DTS difference, though.
OK. And this is something I'm struggling with and thinking about for am335x, we want to make it easy to re-use SoC-specific bits (say memory controller) as well as likely used things (say ethernet). Or are you not quite at the point of number of boards to be able to say whats likely reused but not SoC specific?
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130412/1e93baf7/attachment.pgp>