2008-08-22 Joel Sherrill <joel.sherrill@oarcorp.com>

	* bsp_howto/Makefile.am, bsp_howto/init.t, bsp_howto/intro.t,
	bsp_howto/makefiles.t, bsp_howto/support.t: Update initialization
	sequence. Add another figure.
	* bsp_howto/BSPInitFlowchart-49.eps, bsp_howto/BSPInitFlowchart-49.png: New files.

1 files changed, 19 insertions, 0 deletions

diff --git a/doc/bsp_howto/intro.t b/doc/bsp_howto/intro.t
index cce6302277..1d4c1bdfa6 100644
--- a/doc/bsp_howto/intro.t
+++ b/doc/bsp_howto/intro.t
@@ -55,3 +55,22 @@ this manual as the result of his experiences.  At that time, this
 document was viewed internally as the most important "missing manual"
 in the RTEMS documentation set.
 
+The gen68340 BSP is a good example of the life of an RTEMS BSP.  It is
+based upon a part not recommended for new designs and none of the core RTEMS
+Project team members have one of these boards.  Thus we are unlikely to
+perform major updates on this BSP.  So as long as it compiles and links all
+tests, it will be available.  
+
+The RTEMS Project team members are always trying to identify common
+code across BSPs and refactoring the code into shared routines.
+As part of this effort, the we will enhance the common BSP Framework.
+Not surprisingly, not every BSP takes advantage of every feature in
+the framework.  The gen68340 does not take advantage of as many features
+as the ERC32 BSP does.  So in many ways, the ERC32 is a better example
+BSP at this point.  But even the ERC32 BSP does not include examples
+of every driver template and framework available to the BSP author.
+So in this guide we will try to point out good examples from other BSPs.
+
+Our goal is for you to be able to reuse as much code as possible and
+write as little board specific code as possible.
+