RE: legacy stack or libbsd

2020-09-20 Thread Gabriel.Moyano
>> Hi Chris, >> >>> I will get back around to it. There are 2 sets of changes. In PTP itself a >>> change is to add kqueue support because select in libbsd does not support >>> signals. The PTP code runs a number of timers and they run of an alarm >>> signal. >>> The other piece of support is to

Re: legacy stack or libbsd

2020-09-18 Thread Chris Johns
On 19/9/20 12:45 am, gabriel.moy...@dlr.de wrote: > Hi Chris, > >> I will get back around to it. There are 2 sets of changes. In PTP itself a >> change is to add kqueue support because select in libbsd does not support >> signals. The PTP code runs a number of timers and they run of an alarm >> s

RE: legacy stack or libbsd

2020-09-18 Thread Gabriel.Moyano
Hi Chris, >I will get back around to it. There are 2 sets of changes. In PTP itself a >change is to add kqueue support because select in libbsd does not support >signals. The PTP code runs a number of timers and they run of an alarm signal. >The other piece of support is to the score to bring in t

RE: legacy stack or libbsd

2020-09-16 Thread Gabriel.Moyano
>On 5/8/20 2:13 pm, Gedare Bloom wrote: >> On Tue, Aug 4, 2020 at 6:41 PM Chris Johns wrote: > >>> On 5/8/20 10:23 am, Chris Johns wrote: On 5/8/20 2:04 am, Heinz Junkes wrote: > Because the libbsd stack does not support some things yet (e.g. ntp) > I have PTP running on libbsd. I cu

Re: legacy stack or libbsd

2020-08-04 Thread Chris Johns
On 5/8/20 2:13 pm, Gedare Bloom wrote: > On Tue, Aug 4, 2020 at 6:41 PM Chris Johns wrote: >> >> On 5/8/20 10:23 am, Chris Johns wrote: >>> On 5/8/20 2:04 am, Heinz Junkes wrote: Because the libbsd stack does not support some things yet (e.g. ntp) >>> >>> I have PTP running on libbsd. I curre

Re: legacy stack or libbsd

2020-08-04 Thread Gedare Bloom
On Tue, Aug 4, 2020 at 6:41 PM Chris Johns wrote: > > On 5/8/20 10:23 am, Chris Johns wrote: > > On 5/8/20 2:04 am, Heinz Junkes wrote: > >> Because the libbsd stack does not support some things yet (e.g. ntp) > > > > I have PTP running on libbsd. I currently have no time (ha) to clean up the > >

Re: legacy stack or libbsd

2020-08-04 Thread Chris Johns
On 5/8/20 10:23 am, Chris Johns wrote: > On 5/8/20 2:04 am, Heinz Junkes wrote: >> Because the libbsd stack does not support some things yet (e.g. ntp) > > I have PTP running on libbsd. I currently have no time (ha) to clean up the > work > and create a patch. It requires some extra support in t

Re: legacy stack or libbsd

2020-08-04 Thread Chris Johns
On 5/8/20 2:04 am, Heinz Junkes wrote: > Because the libbsd stack does not support some things yet (e.g. ntp) I have PTP running on libbsd. I currently have no time (ha) to clean up the work and create a patch. It requires some extra support in the score. > I have to call different > functions

Re: legacy stack or libbsd

2020-08-04 Thread Heinz Junkes
Because the libbsd stack does not support some things yet (e.g. ntp) I have to call different functions at rtems_init in EPICS. Therefore, when building EPICS for a target, I need to know which stack the target was built with. Viele Grüße Heinz Junkes -- Experience directly varies with equipme

Re: legacy stack or libbsd

2020-08-04 Thread Joel Sherrill
On Tue, Aug 4, 2020 at 8:10 AM Heinz Junkes wrote: > I'm trying to figure out when compiling a third party software (EPICS), > whether the RTEMS for a target bsp was created with the legacy stack or > uses the libbsd stack. > > Unfortunately I have found some different definitions: > > in target.

legacy stack or libbsd

2020-08-04 Thread Heinz Junkes
I'm trying to figure out when compiling a third party software (EPICS), whether the RTEMS for a target bsp was created with the legacy stack or uses the libbsd stack. Unfortunately I have found some different definitions: in target.cfg : RTEMS_HAS_NETWORKING in bsp.cfg : HAS_NETWORKING in header