1/*  *********************************************************************
2    *  Broadcom Common Firmware Environment (CFE)
3    *  
4    *  TODO
5    *  
6    *  Author:  Mitch Lichtenberg
7    *  
8    *********************************************************************  
9    *
10    *  Copyright 2000,2001,2002,2003
11    *  Broadcom Corporation. All rights reserved.
12    *  
13    *  This software is furnished under license and may be used and 
14    *  copied only in accordance with the following terms and 
15    *  conditions.  Subject to these conditions, you may download, 
16    *  copy, install, use, modify and distribute modified or unmodified 
17    *  copies of this software in source and/or binary form.  No title 
18    *  or ownership is transferred hereby.
19    *  
20    *  1) Any source code used, modified or distributed must reproduce 
21    *     and retain this copyright notice and list of conditions 
22    *     as they appear in the source file.
23    *  
24    *  2) No right is granted to use any trade name, trademark, or 
25    *     logo of Broadcom Corporation.  The "Broadcom Corporation" 
26    *     name may not be used to endorse or promote products derived 
27    *     from this software without the prior written permission of 
28    *     Broadcom Corporation.
29    *  
30    *  3) THIS SOFTWARE IS PROVIDED "AS-IS" AND ANY EXPRESS OR
31    *     IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO, ANY IMPLIED
32    *     WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR 
33    *     PURPOSE, OR NON-INFRINGEMENT ARE DISCLAIMED. IN NO EVENT 
34    *     SHALL BROADCOM BE LIABLE FOR ANY DAMAGES WHATSOEVER, AND IN 
35    *     PARTICULAR, BROADCOM SHALL NOT BE LIABLE FOR DIRECT, INDIRECT,
36    *     INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
37    *     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
38    *     GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
39    *     BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
40    *     OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR 
41    *     TORT (INCLUDING NEGLIGENCE OR OTHERWISE), EVEN IF ADVISED OF 
42    *     THE POSSIBILITY OF SUCH DAMAGE.
43    ********************************************************************* */
44
45
46This file is a quick list of the things that are being considered
47for future development in CFE as it matures.
48
49Customers:  I welcome your comments (good and bad).  
50
51
52------------------------------------------------------------------------------
53FEATURES YET TO BE IMPLEMENTED
54------------------------------------------------------------------------------
55
56* No user interface
57
58   One way we envision CFE being used is with no user interface whatsoever;
59   it will be used to initialize the BCM12500 and launch a program,
60   and that's all.  This configuration might be popular in systems
61   with many BCM12500s, where the slave BCM12500s do not need 
62   console interfaces of their own.
63   
64* Simple scripts
65
66   CFE needs some simple script mechanism (it could be as simple as a set
67   of commands stored in an environment variable), and a way to invoke
68   the script on startup.  For example, such a script could configure
69   the network interface and start a netboot from that interface.
70
71* Power-on Diagnostics
72
73   Once we have a reasonable set of power-on diagnostics, they
74   will be incorporated into the firmware.
75
76* Set/configure serial port baud rate, store rate in flash
77
78* Better "test" commands for tinkering with SOC peripherals
79
80
81------------------------------------------------------------------------------
82FEATURES IN PROGRESS, NOT COMPLETED
83------------------------------------------------------------------------------
84
85* User's Manual improvements
86
87   The user's manual needs to be improved to fill in the missing
88   sections, add additional sections, and convert the style to
89   Broadcom's documentation standards.  You'll be able to get
90   the latest manuals from DocSafe when this happens.
91
92* Some API functions not implemented
93
94   Several of the API functions available via CFE's external API are not
95   implemented, or are missing features.
96
97
98------------------------------------------------------------------------------
99IDEAS THAT WON'T NECESSARILY BE DONE
100------------------------------------------------------------------------------
101
102* Write access to file systems
103 
104   Write access to file systems is specifically *not* included in CFE for
105   simplicity.  
106
107* Direct support for reading boot files via NFS
108
109   This is outside the design goals for CFE, but given enough requests
110   it can be done easily.
111
112
113------------------------------------------------------------------------------
114
115
116  
117