Re: Disable libnetwork on Epiphany?

> On 16 Aug 2018, at 3:31 am, Joel Sherrill wrote: >> On Tue, Aug 14, 2018 at 4:26 AM, Hesham Almatary >> wrote: >> On Tue, Aug 14, 2018 at 10:17 AM, Joel Sherrill wrote: >> > >> > >> > On Tue, Aug 14, 2018, 2:51 AM Hesham Almatary >> > wrote: >> >> >> >> AFAIR, I've never tried epiphany with

Re: git.rtems.org LetsEncrypt TLS certificate expired

On 15/8/18 11:19 pm, Amaan Cheval wrote: > FYI: https://docs.rtems.org has an expired certificate too. > > On Wed, Aug 15, 2018 at 3:30 PM, Amaan Cheval wrote: >> The HTTPS certificate for https://git.rtems.org has expired (~15 >> minutes ago). Are the auto-renewal scripts failing? Thank you for

Flight Software Workshop Abstracts and Registration

Hi The Flight Software Workshop is being held this year December 3-6 at the Southwest Research Institute in San Antonio, Texas. The website is: http://flightsoftware.jhuapl.edu/ This is a presentation only conference but the deadline for submissions is Monday. Important Dates: Abstracts Submi

Re: Disable libnetwork on Epiphany?

On Tue, Aug 14, 2018 at 4:26 AM, Hesham Almatary wrote: > On Tue, Aug 14, 2018 at 10:17 AM, Joel Sherrill wrote: > > > > > > On Tue, Aug 14, 2018, 2:51 AM Hesham Almatary > > wrote: > >> > >> AFAIR, I've never tried epiphany with networking. The cores are > >> supposed to be accelerators, so th

Re: [PATCH] dev/sc16is752: Add name space for field names.

Thanks Christian! This does indeed resolve the warning on psim so it should be ok on all other powerpc BSPs. I will build all powerpc BSPs to double check and then push. --joel On Wed, Aug 15, 2018 at 5:26 AM, wrote: > From: Christian Mauderer > > The field names for the registers generated a

[PATCH] Tests for inttypes methods

--- testsuites/psxtests/Makefile.am| 12 ++ testsuites/psxtests/configure.ac | 1 + testsuites/psxtests/psxinttypes01/init.c | 122 + .../psxtests/psxinttypes01/psxinttypes01.scn | 27 + 4 files changed, 162 insertio

Re: git.rtems.org LetsEncrypt TLS certificate expired

FYI: https://docs.rtems.org has an expired certificate too. On Wed, Aug 15, 2018 at 3:30 PM, Amaan Cheval wrote: > The HTTPS certificate for https://git.rtems.org has expired (~15 > minutes ago). Are the auto-renewal scripts failing? ___ devel mailing l

[PATCH 0/1] dev/sc16is752: Add name space for field names.

Hello, this patch should fix https://devel.rtems.org/ticket/3501. Note that I didn't test it yet because I have some trouble building a tool chain on my home PC. If no one is faster, I'll try it either if I manage to get a working tool chain or on Monday when I'm back at work. Best regards Chris

[PATCH] dev/sc16is752: Add name space for field names.

From: Christian Mauderer The field names for the registers generated a name collision (MSR_RI on the power pc). This patch adds a SC16IS752_ prefix for all field names. Closes #3501. --- cpukit/dev/serial/sc16is752-regs.h | 108 ++--- cpukit/dev/serial/sc16is752.c |

git.rtems.org LetsEncrypt TLS certificate expired

The HTTPS certificate for https://git.rtems.org has expired (~15 minutes ago). Are the auto-renewal scripts failing? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: covoar SIGKILL Investigation

On 15/8/18 2:47 am, Joel Sherrill wrote: > > Ideas appreciated on how to debug this enough to find > the cause. > Does the attached patch help? Chris diff --git a/tester/covoar/ExecutableInfo.cc b/tester/covoar/ExecutableInfo.cc index 0a629b7..d93860b 100644 --- a/tester/covoar/ExecutableInfo.c