[PATCH] Update FreeBSD kernel timespec support

This change is based on the following FreeBSD commit: "Make timespecadd(3) and friends public The timespecadd(3) family of macros were imported from NetBSD back in r35029. However, they were initially guarded by #ifdef _KERNEL. In the meantime, we have grown at least 28 syscalls that use timespec

Re: Some problems with the libbsd update

On Thu, Aug 23, 2018 at 12:15 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 23/08/18 01:13, Joel Sherrill wrote: > >> >> >> On Wed, Aug 22, 2018 at 6:00 PM, Chris Johns > chr...@rtems.org>> wrote: >> >> On 22/08/2018 22:25, Sebastian Huber wrote: >> > On 22/08/18 14

Re: Some problems with the libbsd update

On 23/08/18 15:40, Joel Sherrill wrote: An even when an architecture has the infrastructure, there is at least the SPARC which I don't think have any Nexus devices

Re: Some problems with the libbsd update

On 23/08/18 15:40, Joel Sherrill wrote: On Thu, Aug 23, 2018 at 12:15 AM, Sebastian Huber > wrote: On 23/08/18 01:13, Joel Sherrill wrote: On Wed, Aug 22, 2018 at 6:00 PM, Chris Johns mailto:chr...@rtems.org>

Re: Some problems with the libbsd update

Hello, I ignored this epoch memory reclamation problem and continued with the update. I reach the FreeBSD head today. It seems that this epoch memory reclamation and the use of Concurrency Kit is the only big issue. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Pu

Proposal for procedure for architecture/BSP removal

Hello, I would like to propose a procedure for architecture/BSP removal since I think the RTEMS master carries to much historic ballast around with no active user base. Once the release branch is created, an announcement is placed on the devel and users mailing lists and the web site news. The

Re: Aligned operations mismatch

Yes, I use the legacy network stack (I did not know it is legacy, Do you have any plans to remove it from source?). I will create the ticket and I will send the patch. Best regards, Mikhail On Thu, 23 Aug 2018 at 07:33, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 23/08/18

Re: Proposal for procedure for architecture/BSP removal

On 24/08/2018 03:51, Sebastian Huber wrote: > I would like to propose a procedure for architecture/BSP removal since I > think the RTEMS master carries to much historic ballast around with no active > user base. For example? We have a history of following gcc. Are you proposing we move away from

Re: Some problems with the libbsd update

On 23/08/2018 23:54, Sebastian Huber wrote: > On 23/08/18 15:40, Joel Sherrill wrote: >> On Thu, Aug 23, 2018 at 12:15 AM, Sebastian Huber >> > > wrote: >> >>     On 23/08/18 01:13, Joel Sherrill wrote: >> >> >> >>     On Wed, Aug 22, 2018 at 6:00 PM,

Re: Some problems with the libbsd update

On 24/08/18 04:13, Chris Johns wrote: On 23/08/2018 23:54, Sebastian Huber wrote: On 23/08/18 15:40, Joel Sherrill wrote: On Thu, Aug 23, 2018 at 12:15 AM, Sebastian Huber mailto:sebastian.hu...@embedded-brains.de>> wrote:     On 23/08/18 01:13, Joel Sherrill wrote:     On Wed, Aug 22

Re: Some problems with the libbsd update

On 24/08/2018 15:31, Sebastian Huber wrote: > > Could you then please make suggestions what should be placed where? Is the > User > Manual the landing point for users? This information could be added here: > > https://docs.rtems.org/branches/master/user/bsps/index.html > Sure, I will put this