One way to keep this in sync would be to simply write the README of each
BSP in a certain format, e.g. trac wiki and then simply include the
content from Git in trac. For example via a modified variant of
https://trac.edgewall.org/attachment/wiki/MacroBazaar/Include.3.py
Something like this i
Hello Chris,
On Tuesday 04 of October 2016 23:10:20 Chris Johns wrote:
> On 04/10/2016 09:51, Pavel Pisa wrote:
> > Hello Chris and Joel,
> >
> > I would like to correct my mistake which breaks RTEMS 4.11 build for
> > non-ARM architectures, as fast as possible. Proposed solution on devel
> > list
On 04/10/2016 09:51, Pavel Pisa wrote:
Hello Chris and Joel,
I would like to correct my mistake which breaks RTEMS 4.11 build for non-ARM
architectures, as fast as possible. Proposed solution on devel list.
[PATCH] libdl/rtl-obj.c: synchronize cache should not depend on
CPU_CACHE_LINE_BYTES.
On 05/10/2016 01:20, Joel Sherrill wrote:
Well.. looking at the log, I think the answer is that rtems-syms is not
processing the "-EL" option on the MIPS.
It looks to me like it is but rtems-syms is not handling it correctly.
Thus the objects are always
big endian on the MIPS but three BSPs u
Hello Gedare and Alexander,
one possible solution to keep that in sync.
Change of README in BSP directory
to MarkDown or Rest-Text syntax and put on the web
generated pages synced directly from master and last stable.
On the other hand, wiki allows to include more information
and relation links.
Well.. looking at the log, I think the answer is that rtems-syms is not
processing the "-EL" option on the MIPS. Thus the objects are always
big endian on the MIPS but three BSPs use the -EL option.
mips-rtems4.12-gcc -B../../../../../hurricane/lib/ -specs bsp_specs -qrtems
-mips3 -G0 -EL -O2 -g -
Sending a build log privately.
On Mon, Oct 3, 2016 at 5:02 PM, Chris Johns wrote:
> On 04/10/2016 02:57, Joel Sherrill wrote:
>
>>
>> Looking at failures from a build sweep.
>>
>> I think this one is known but am passing along. The rtbx4925, rtbx4938,
>> and hurricane fail with this:
>>
>> -
Thanks. does this BSP have a wiki page? If not, it would be good to
make one for it. Generally we need to do a better job of keeping a
web-visible "feature set" up to date.
On Tue, Oct 4, 2016 at 7:39 AM, Alexander Krutwig
wrote:
> Hello,
>
> over the last months, lots of work and effort has been
Hello,
over the last months, lots of work and effort has been put into the
development
of the BSP support for ATSAMV7 microcontrollers by Atmel.
Thus, I updated the README of the BSP with the work already done in the
process and
attached it to this email in order to keep you updated about the
Hello,
there are still some seats available, so here is our final announcement:
we are currently planning an open RTEMS class "RTEMS Application
Development" in Munich/Germany to start on
October 18th, 2016.
This class has is main focus on application development based on the
R
10 matches
Mail list logo
