<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Till Straumann wrote:<br>
<blockquote type="cite" cite="mid47623FEC.6000302@slac.stanford.edu">
<pre wrap="">Ralf Corsepius wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, 2007-12-12 at 21:27 -0700, Andrei Chichak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks Joel,
Are there any docs around dealing with putting together a new BSP? I
have taken a look at the BSP and porting guides but there doesn't
seem to be a section on which configuration files to munge to get the
bootstrap procedure to pick up the new BSP.
</pre>
</blockquote>
<pre wrap="">Well, actually, it's pretty simple.
1. cd <src>/c/src/lib/libbsp/<cpu>
and copy over the BSP which resembles to your BSP most
cp <bsp> <mybsp>
2. edit your bsp's files below <mybsp>/
[The actual act of porting]
</pre>
</blockquote>
<pre wrap=""><!---->
If I may comment: that would be pretty bad practice.
A better way would be
- make parts in <bsp> that are similar enough to what
'mybsp' needs a library that supports both, <bsp> and
<mybsp>. Try to make interfaces generic enough so that
they could be useful to a yet more similar BSP that
may be created in the future (but also: try to keep it simple).
- modify <bsp> so it uses the (new) library
- let <mybsp> use the library
- only add new parts that are really specific to <mybsp>
The myriad of powerpc BSPs are a painful example of
the result of the 'copy + edit' strategy when creating new
BSPs. It's maintenance hell.</pre>
</blockquote>
I somehow agree with what Ralf Corsepius wrote :<br>
<pre wrap="">> The poor shape the powerpc BSPs are in is a result of lack of RTEMS
<span class="moz-txt-citetags">> </span>internal APIs and structural defects of the source code (esp. the
<span class="moz-txt-citetags">> </span>"shared" dirs).
Technically speaking, to reduce maintence effort effectively, one
should start to think about C++ for Object Orient Programming.
Kate
</pre>
<blockquote type="cite" cite="mid47623FEC.6000302@slac.stanford.edu">
<pre wrap="">
T.
</pre>
<blockquote type="cite">
<pre wrap="">
3. cd <src>/c/src
../../bootstrap
The next configure run should pick up <mybsp> automatically.
Ralf
_______________________________________________
rtems-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtems-users@rtems.com">rtems-users@rtems.com</a>
<a class="moz-txt-link-freetext" href="http://rtems.rtems.org/mailman/listinfo/rtems-users">http://rtems.rtems.org/mailman/listinfo/rtems-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
rtems-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rtems-users@rtems.com">rtems-users@rtems.com</a>
<a class="moz-txt-link-freetext" href="http://rtems.rtems.org/mailman/listinfo/rtems-users">http://rtems.rtems.org/mailman/listinfo/rtems-users</a>
</pre>
</blockquote>
<br>
</body>
</html>