On 26/07/18 08:10, Sebastian Huber wrote:
Hello,
the or1k ecosystem has a major problem with their non-FSF GCC from my
point of view which is maintained here:
https://github.com/openrisc/or1k-gcc
The last commit was in 2016. It looks like a dead project to me.
Given the momentum RISC-V has
Move the kernel space content of some Newlib provided header files to
RTEMS and libbsd. This allows to use the Newlib provided header files
with different FreeBSD baselines.
Update #3472.
---
rtemsbsd/include/machine/_kernel_if.h | 48 ++
rtemsbsd/include/machine/_kernel_sock
Remove unused files which may make trouble during FreeBSD baseline
updates. It also increased the compile-time of the library for nothing.
Update #3472.
---
freebsd/contrib/wpa/src/rsn_supp/tdls.c | 3054 --
freebsd/contrib/wpa/wpa_supplicant/wnm_sta.c | 1168 ---
This is a workaround for the FreeBSD kernel space source file
sys/opencrypto/xform.c
which includes a bunch of *.c files.
Update #3472.
---
builder.py | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/builder.py b/builder.py
index 78f592c7b..7f4e71705 100755
--- a
Hi!
Seems like rtems.org now has this issue.
On Thu, Aug 16, 2018 at 6:09 AM Chris Johns wrote:
>
> 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 certificat
Hi,
Regarding or1k, we (ÅAC Microtec/Clyde Space) are currently using it,
together with RTEMS, in some of our products[0], and are thus quite
interested in its continued life as a part of RTEMS, at least in the
foreseeable future (i.e. RTEMS 5).
With regards to the upstreaming of GCC, there are s
On Fri, Aug 24, 2018, 7:04 AM Martin Erik Werner <
martinerikwerner@gmail.com> wrote:
> Hi,
>
> Regarding or1k, we (ÅAC Microtec/Clyde Space) are currently using it,
> together with RTEMS, in some of our products[0], and are thus quite
> interested in its continued life as a part of RTEMS, at
From: Daniel Cederman
If the floating point trap occurred in a delay slot it is not certain
that npc will be equal to pc + 4.
---
cpukit/score/cpu/sparc/syscall.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/score/cpu/sparc/syscall.S b/cpukit/score/cpu/sparc/syscall
Missed to enable interrupt per TX descriptor. Could lead to TX buffer
starvation.
Does not affect the GBit code.
---
bsps/sparc/shared/net/greth.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/bsps/sparc/shared/net/greth.c b/bsps/sparc/shared/net/greth.c
index eaf
ince some time RTEMS started to use the termios c_ispeed and
c_ospeed variables in the termios struct to hold the UART baudrate.
However the APBUART driver still uses the old c_cflag sometimes
causing other UART parameters to get overwritten, for example the
partiy setting no mapped to the same bit
To clarify, SMP with GRSWP_PKT driver API has been extended to
take advantage of multi-core, is now SMP-safe, and has been tested
on GR740.
---
bsps/sparc/shared/spw/grspw_pkt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bsps/sparc/shared/spw/grspw_pkt.c
b/bsps/sparc/shar
This avoids an exception (FP disabled) when RTEMS/Newlib have
been built with LLVM/Sparc.
---
testsuites/psxtests/psx13/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/testsuites/psxtests/psx13/main.c b/testsuites/psxtests/psx13/main.c
index aee8b78..05909a2 100644
--- a/testsuites/ps
Declare i volatile to avoid compiler optimization putting i
into data section with initialization value 1.
---
testsuites/sptests/spglobalcon01/init.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/testsuites/sptests/spglobalcon01/init.cc
b/testsuites/sptests/spglobalcon
---
bsps/sparc/shared/start/start.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bsps/sparc/shared/start/start.S b/bsps/sparc/shared/start/start.S
index 48072e8..0be93ed 100644
--- a/bsps/sparc/shared/start/start.S
+++ b/bsps/sparc/shared/start/start.S
@@ -310,7 +310,7 @@ SY
It enabled promiscous mode or sets the multicast filter according
to the configuration and parameters to ioctl(SIOCSIFFLAGS),
ioctl(SIOCADDMULTI) and ioctl(SIOCDELMULTI).
On SIOCADDMULTI/SIOCDELMULTI requests the greth ioctl calls the
Ethernet helper functions ether_addmulti()/ether_delmulti() whic
LLVM warns about this:
cpukit/libmisc/capture/capture.c:405:30: warning:
taking address of packed member 'time' of class or structure
'rtems_capture_record' may result in an unaligned pointer value
[-Waddress-of-packed-member]
rtems_capture_get_time (&in.time);
And on sparc
This avoids an exception (FP disabled) when RTEMS/Newlib have
been built with LLVM/Sparc.
---
testsuites/psxtests/psxfile01/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/testsuites/psxtests/psxfile01/main.c
b/testsuites/psxtests/psxfile01/main.c
index c634082..5ccdd6b 100644
--- a/
Hello Daniel,
the patch set looks good, please check it in.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on requ
Thanks for the quick review. I will push it in.
I will be posting some more patches next week that we have in the pipe,
some related to the LLVM development work we are doing.
Regards, Daniel
On 2018-08-24 15:43, Sebastian Huber wrote:
Hello Daniel,
the patch set looks good, please check i
19 matches
Mail list logo
