Re: AW: AW: AW: [PATCH] kern_tc.c: Update pps_event() for uniprocessor configurations

On 08.06.22 09:54, gabriel.moy...@dlr.de wrote: I don't know why there is this "if" in the code. I will ask on a FreeBSD mailing list. I think it is for the case that th_generation has changed in between saving the th and th_counter. If this happens pps->capgen is set to 0 and later pps_event(

[libbsd 9/9] build: Do not require RTEMS_POSIX_API

--- wscript | 4 1 file changed, 4 deletions(-) diff --git a/wscript b/wscript index bfdcc91c..7b8f4d31 100644 --- a/wscript +++ b/wscript @@ -170,10 +170,6 @@ def options(opt): def bsp_configure(conf, arch_bsp): conf.check(header_name="dlfcn.h", features="c") conf.check(header_na

[libbsd 4/9] openssl: Do not use signals

--- freebsd/crypto/openssl/apps/ocsp.c | 2 +- freebsd/crypto/openssl/apps/openssl.c | 2 ++ .../crypto/openssl/apps/rtems-bsd-openssl-ocsp-data.h | 2 -- freebsd/crypto/openssl/crypto/ui/ui_openssl.c | 10 ++ 4 files changed, 13 insertions

[libbsd 8/9] netstat: Do not use signals

--- freebsd/usr.bin/netstat/if.c | 19 --- .../netstat/rtems-bsd-netstat-if-data.h | 2 -- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/freebsd/usr.bin/netstat/if.c b/freebsd/usr.bin/netstat/if.c index c578629e..ffb639c6 100644 --- a/freeb

[libbsd 7/9] wlanstats: Do not use signals

--- freebsd/tools/tools/net80211/wlanstats/main.c | 22 +++ .../wlanstats/rtems-bsd-wlanstats-main-data.h | 2 -- 2 files changed, 8 insertions(+), 16 deletions(-) diff --git a/freebsd/tools/tools/net80211/wlanstats/main.c b/freebsd/tools/tools/net80211/wlanstats/main.c index 3a

[libbsd 6/9] ping6: Do not use signals

--- freebsd/sbin/ping6/ping6.c | 16 1 file changed, 16 insertions(+) diff --git a/freebsd/sbin/ping6/ping6.c b/freebsd/sbin/ping6/ping6.c index 96bd60e3..67ad46eb 100644 --- a/freebsd/sbin/ping6/ping6.c +++ b/freebsd/sbin/ping6/ping6.c @@ -287,7 +287,9 @@ static void fill(char

[libbsd 0/9] Remove dependency on RTEMS_POSIX_API

Sebastian Huber (9): ipsec-tools: Do not use signals wpa: Do not use signals wpa: Use CONFIG_ELOOP_KQUEUE openssl: Do not use signals ping: Do not use signals ping6: Do not use signals wlanstats: Do not use signals netstat: Do not use signals build: Do not require RTEMS_POSIX_API

[libbsd 1/9] ipsec-tools: Do not use signals

--- ipsec-tools/src/racoon/privsep.c | 12 +- .../racoon/rtems-bsd-racoon-session-data.h| 3 --- ipsec-tools/src/racoon/session.c | 23 +++ 3 files changed, 24 insertions(+), 14 deletions(-) diff --git a/ipsec-tools/src/racoon/privsep.c b/ips

[libbsd 5/9] ping: Do not use signals

--- freebsd/sbin/ping/ping.c | 8 1 file changed, 8 insertions(+) diff --git a/freebsd/sbin/ping/ping.c b/freebsd/sbin/ping/ping.c index 71976058..0daa5f45 100644 --- a/freebsd/sbin/ping/ping.c +++ b/freebsd/sbin/ping/ping.c @@ -306,7 +306,9 @@ main(int argc, char *const *argv) #endif

[libbsd 2/9] wpa: Do not use signals

--- freebsd/contrib/wpa/src/utils/eloop.c | 16 1 file changed, 16 insertions(+) diff --git a/freebsd/contrib/wpa/src/utils/eloop.c b/freebsd/contrib/wpa/src/utils/eloop.c index 41de0f79..b26de5a0 100644 --- a/freebsd/contrib/wpa/src/utils/eloop.c +++ b/freebsd/contrib/wpa/src/u

[libbsd 3/9] wpa: Use CONFIG_ELOOP_KQUEUE

This avoids issues with the fd_set size. --- freebsd/contrib/wpa/src/utils/eloop.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/freebsd/contrib/wpa/src/utils/eloop.c b/freebsd/contrib/wpa/src/utils/eloop.c index b26de5a0..09493b89 100644 --- a/freebsd/contrib/wpa/src/utils/eloop.c +++ b

Re: Does libbsd really require POSIX enabled now?

On 09/06/2022 15:50, Sebastian Huber wrote: Technically, it should be a big issue. Technically, it should NOT be a big issue. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-1

Static Analysis Tools for RTEMS

Hi With Matthew addressing new warnings from GCC 12, I thought it would be good to remind everyone that the RTEMS Project has access to two static analysis tools. As you work, fix bugs/warnings, etc., please remember to look at the results for the area of code you are touching from the static anal

Re: [gcc] Enable TLS support for RTEMS in libstdc++

On 09/06/2022 15:58, Joel Sherrill wrote: On Thu, Jun 9, 2022 at 2:12 AM Chris Johns > wrote: On 9/6/2022 4:16 pm, Sebastian Huber wrote: > On 08/06/2022 16:18, Sebastian Huber wrote: >> On 08/06/2022 16:11, Joel Sherrill wrote: >>> On Wed, Jun 8,

Re: [gcc] Enable TLS support for RTEMS in libstdc++

On Thu, Jun 9, 2022 at 2:12 AM Chris Johns wrote: > On 9/6/2022 4:16 pm, Sebastian Huber wrote: > > On 08/06/2022 16:18, Sebastian Huber wrote: > >> On 08/06/2022 16:11, Joel Sherrill wrote: > >>> On Wed, Jun 8, 2022 at 8:47 AM Sebastian Huber > >>> >>>

Re: Does libbsd really require POSIX enabled now?

On 09/06/2022 15:44, Joel Sherrill wrote: Are there any features besides signals and sporadic scheduling that are enabled anymore? Removing the requirement for RTEMS_POSIX_API for libbsd is just one item on my long TODO list. Technically, it should be a big issue. Some commands may still use

Does libbsd really require POSIX enabled now?

Hi I'm starting a new thread because Frank's documentation thread is long enough already. From that thread: === > I also question why you say RTEMS_POSIX_API needs to be True. That > does not enable much anymore. I only know of signals and the Sporadic > Scheduler. > Because w

[PATCH rtems-docs v2] TFTPFS: New documentation

From: Frank Kühndel --- filesystem/index.rst | 1 + filesystem/trivial_ftp.rst | 564 - 2 files changed, 562 insertions(+), 3 deletions(-) diff --git a/filesystem/index.rst b/filesystem/index.rst index f4e2ed6..64a2f1d 100644 --- a/filesystem/index.rs

Re: [PATCH rtems-docs 1/1] TFTPFS: New documentation

Hello Chris, Hello Joel, Hello Sebastian, many thanks for your reviews and comments. I will send an updated v2 of this patch. It will take your comments in account. On 6/7/22 18:56, Joel Sherrill wrote: > > On Sun, Jun 5, 2022 at 8:56 PM Chris Johns wrote: > >> Hi Frank, >> >> Thanks for the d

Re: [PATCH] user/bsps/arm: Second Ethernet on i.MX

Hello Chris, Am 09.06.22 um 09:20 schrieb Chris Johns: OK push. Thanks. (I am not familiar with these devices so ...) Is the needed device tree fragments easily available to the user? The device tree for the i.MX6 and i.MX7 series are basically just the ones from FreeBSD or Linux. So the

Re: [PATCH] user/bsps/arm: Second Ethernet on i.MX

OK push. (I am not familiar with these devices so ...) Is the needed device tree fragments easily available to the user? Thanks Chris On 9/6/2022 5:03 pm, Christian Mauderer wrote: > This adds information how to use a second Ethernet controller on the > i.MX BSPs. > --- > user/bsps/arm/imx.rst

Re: [gcc] Enable TLS support for RTEMS in libstdc++

On 9/6/2022 4:16 pm, Sebastian Huber wrote: > On 08/06/2022 16:18, Sebastian Huber wrote: >> On 08/06/2022 16:11, Joel Sherrill wrote: >>> On Wed, Jun 8, 2022 at 8:47 AM Sebastian Huber >>> >> > wrote: >>> >>>     On 08/06/2022 15:39, Joel Sherrill wrote:

Re: [PATCH rtems v2] bsps/imx: Enable clock of ETH2

Thanks for the review and the OK to push. I created a patch for rtems-docs that gives some information about that (and about how to use the second Ethernet controller) and sent it to the list. Am 08.06.22 um 02:49 schrieb Chris Johns: Does the BSP doco in the User Manual need updating to men

[PATCH] user/bsps/arm: Second Ethernet on i.MX

This adds information how to use a second Ethernet controller on the i.MX BSPs. --- user/bsps/arm/imx.rst | 17 + 1 file changed, 17 insertions(+) diff --git a/user/bsps/arm/imx.rst b/user/bsps/arm/imx.rst index ee98f0b..e2fd7f2 100644 --- a/user/bsps/arm/imx.rst +++ b/user/bsps/a