On 20/09/2017 15:08, Chris Johns wrote:
>
> Is it worth running? I am wondering about hard coding a filter to not run it
> in
> rtems-test runs.
>
I have add test failure exceptions and minimum is the only hard coded entry. If
this test runs and does not time out it is marked as a pass.
Chris
Signed-off-by: Sebastian Huber
---
newlib/libc/sys/rtems/include/sys/_pthreadtypes.h | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/newlib/libc/sys/rtems/include/sys/_pthreadtypes.h
b/newlib/libc/sys/rtems/include/sys/_pthreadtypes.h
index 9db50fe44..6ffedaebf 100644
Update #3114.
---
cpukit/libcsupport/include/rtems/libcsupport.h| 1 -
cpukit/libcsupport/src/resource_snapshot.c| 1 -
cpukit/posix/Makefile.am | 3 +-
cpukit/posix/include/rtems/posix/barrier.h| 64 -
cpukit/posix/include/rtems/posi
On Thu, Sep 21, 2017 at 2:27 AM, Chris Johns wrote:
> On 20/09/2017 15:08, Chris Johns wrote:
> >
> > Is it worth running? I am wondering about hard coding a filter to not
> run it in
> > rtems-test runs.
> >
>
> I have add test failure exceptions and minimum is the only hard coded
> entry. If
>
Hi,
I am running RTEMS 4.10 on a LEON3 processor.
Has anyone succeeded in making interruptions with SPW up and running ?
Because I am quite stuck there, the example in RTEMS (rtems_irq.c) is
not designed for LEON3 and in the drivers documentation given by
Gaisler, they say that we can connec
On 22/09/2017 01:24, Joel Sherrill wrote:
>
> The intent of this test is to demonstrate the smallest executable and
> data size possible.
>
That runs?
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On Sep 21, 2017 6:30 PM, "Chris Johns" wrote:
On 22/09/2017 01:24, Joel Sherrill wrote:
>
> The intent of this test is to demonstrate the smallest executable and
> data size possible.
>
That runs?
Yes. There is no requirement that an RTEMS application include the test
framework or even a conso
On 22/09/2017 12:30, Joel Sherrill wrote:
> Yes. There is no requirement that an RTEMS application include the test
> framework or even a console driver.
Agreed. I have made it a pass if the target does not time out.
Chris
___
devel mailing list
devel@r
Hello Yannick,
if you want to use the GR712RC, then I would definitely update to RTEMS
4.12. Gaisler integrated all their drivers and they are now up to date.
In addition the GCC used with RTEMS 4.12 contains an errata fix for the
GR712RC.
--
Sebastian Huber, embedded brains GmbH
Address :
Hi,
I built u-boot from the git master repo for the Beaglebone Black and I have been
working with an RTEMS u-boot type image plus a local patch to by pass
`bsp_fdt_copy` that is now called for this board. With the change there is a
crash as `r3` is not valid with the RTEMS OS entry.
I have also t
> Hi,
>
> I built u-boot from the git master repo for the Beaglebone Black and I have
> been
> working with an RTEMS u-boot type image plus a local patch to by pass
> `bsp_fdt_copy` that is now called for this board. With the change there is a
> crash as `r3` is not valid with the RTEMS OS entry.
On 22/09/2017 16:13, Sichen Zhao wrote:
> Can you please tell me which version of u-boot you used?
> My version is old: U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 -
> 13:23:54)
I built git://git.denx.de/u-boot.git master and I think commit
8a1c44271c55961fb70fb6177f9c02fdb05287c5. Looking at
12 matches
Mail list logo