From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README: Give an explicit example of adding a new board.
Date: Tue, 17 Nov 2009 04:22:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911170419590.9417@localhost> (raw)
Explicitly demonstrate an example (BeagleBoard) of what was
added/changed to support a new board.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
obviously not critical, but it might be useful for readers to see
explicitly what constitutes adding support for a new board, file by
file. your choice to apply it or not. i *think* i got everything.
diff --git a/README b/README
index 2c77687..cc701b1 100644
--- a/README
+++ b/README
@@ -2874,6 +2874,73 @@ steps:
[Of course, this last step is much harder than it sounds.]
+A real-life example of adding a new board
+=========================================
+
+ As a working example of adding a new board, consider the files
+and directories that were added/changed to support the OMAP3-based
+BeagleBoard.
+
+ First, the new files:
+
+ ./board/ti/beagle/
+ beagle.c
+ beagle.h
+ config.mk
+ Makefile
+ ./include/configs/omap3_beagle.h
+
+Followed by changes to existing files:
+
+ Makefile
+ ========
+
+ omap3_beagle_config : unconfig
+ @$(MKCONFIG) $(@:_config=) arm arm_cortexa8 beagle ti omap3
+
+ MAKEALL
+ =======
+
+ LIST_ARM_CORTEX_A8=" \
+ devkit8000 \
+ omap3_beagle \
+ omap3_overo \
+ ...
+
+ include/asm-arm-types.h
+ =======================
+
+ #ifdef CONFIG_MACH_OMAP3_BEAGLE
+ # ifdef machine_arch_type
+ # undef machine_arch_type
+ # define machine_arch_type __machine_arch_type
+ # else
+ # define machine_arch_type MACH_TYPE_OMAP3_BEAGLE
+ # endif
+ # define machine_is_omap3_beagle() (machine_arch_type == MACH_TYPE_OMAP3_BEAGLE)
+ #else
+ # define machine_is_omap3_beagle() (0)
+ #endif
+
+ doc/README.omap3
+ ================
+
+ Build
+ =====
+
+ * BeagleBoard:
+
+ make omap3_beagle_config
+ make
+
+ MAINTAINERS
+ ===========
+
+ Dirk Behme <dirk.behme@gmail.com>
+
+ omap3_beagle ARM CORTEX-A8 (OMAP3530 SoC)
+
+
Testing of U-Boot Modifications, Ports to New Hardware, etc.:
==============================================================
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-11-17 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:22 Robert P. J. Day [this message]
2009-11-17 10:02 ` [U-Boot] [PATCH] README: Give an explicit example of adding a new board Dirk Behme
2009-11-17 10:26 ` Robert P. J. Day
2009-11-17 12:01 ` Wolfgang Denk
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=alpine.LFD.2.00.0911170419590.9417@localhost \
--to=rpjday@crashcourse.ca \
--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