On Tue, 17 Nov 2009, Dirk Behme wrote:
Robert P. J. Day wrote:
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.cbeagle.hconfig.mkMakefile- ./include/configs/omap3_beagle.h
Most probably the naming convention guys here want some hints about correct directory and config file names ;)
just to be clear, i wasn't trying to give methodical directions for *how* to add a board, just a summary of what the *end result* might be if someone wanted to see them. so, in a sense, i'm not trying to duplicate the instructions for how to add a board, just let people see what it ultimately represents.
i just threw this together since *i* was curious about what ended up in the code base to support a single board and i figured others might want a summary, that's all.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================