date:20230413

Re: [rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

2023-04-13 Thread Chris Johns

On 14/4/2023 3:40 pm, Vijay Kumar Banerjee wrote:
> 
> The patch looks great. Thanks.

Thanks for quick review. I will push it.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

2023-04-13 Thread Vijay Kumar Banerjee

Hi Chris,

The patch looks great. Thanks.

On Thu, Apr 13, 2023 at 11:21 PM  wrote:
>
> From: Chris Johns 
>
> ---
>  include/rtems/rtems-net-legacy.h.in | 42 +
>  netlegacy.py| 35 +---
>  rtems_waf   |  2 +-
>  3 files changed, 75 insertions(+), 4 deletions(-)
>  create mode 100755 include/rtems/rtems-net-legacy.h.in
>
> diff --git a/include/rtems/rtems-net-legacy.h.in 
> b/include/rtems/rtems-net-legacy.h.in
> new file mode 100755
> index 000..a17ec21
> --- /dev/null
> +++ b/include/rtems/rtems-net-legacy.h.in
> @@ -0,0 +1,42 @@
> +/**
> + * @file
> + *
> + * @ingroup rtems_net_legacy
> + *
> + * @brief This file is generated
> + */
> +
> +/*
> + * Copyright (c) 2023. Chris Johns . All rights reserved.
> + *
> + * Redistribution and use in source and binary forms, with or without
> + * modification, are permitted provided that the following conditions
> + * are met:
> + * 1. Redistributions of source code must retain the above copyright
> + *notice, this list of conditions and the following disclaimer.
> + * 2. Redistributions in binary form must reproduce the above copyright
> + *notice, this list of conditions and the following disclaimer in the
> + *documentation and/or other materials provided with the distribution.
> + *
> + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
> + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> + * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
> + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
> + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
> + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
> + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> + * SUCH DAMAGE.
> + */
> +
> +#ifndef _RTEMS_NET_LGEACY_H_
> +#define _RTEMS_NET_LEGACY_H_
> +
> +#define RTEMS_NET_LEGACY_VERSION  @RTEMS_NET_LEGACY_VERSION@
> +
> +#define RTEMS_NET_LEGACY_MAJOR@RTEMS_NET_LEGACY_MAJOR@
> +#define RTEMS_NET_LEGACY_REVISION @RTEMS_NET_LEGACY_REVISION@
> +
> +#endif /* _RTEMS_NET_LGEACY_H_ */
> diff --git a/netlegacy.py b/netlegacy.py
> index 60775dc..9f27ffc 100644
> --- a/netlegacy.py
> +++ b/netlegacy.py
> @@ -29,12 +29,31 @@
>  import os
>  import os.path
>
> +from rtems_waf import git
>  from rtems_waf import rtems
> +from rtems_waf import version
>
>  import bsp_drivers
>  import netsources
>
>
> +def version_header(bld):
> +versions = {
> +'RTEMS_NET_LEGACY_VERSION':
> +'"' + bld.env.RTEMS_NET_LEGACY_VERSION + '"',
> +'RTEMS_NET_LEGACY_MAJOR': bld.env.RTEMS_NET_LEGACY_MAJOR,
> +'RTEMS_NET_LEGACY_REVISION':
> +'"' + bld.env.RTEMS_NET_LEGACY_REVISION + '"',
> +}
> +sed = 'sed '
> +for cfg in versions:
> +sed += "-e 's/@%s@/%s/' " % (cfg, versions[cfg])
> +bld(target='include/rtems/rtems-net-legacy.h',
> +source='include/rtems/rtems-net-legacy.h.in',
> +rule=sed + ' < ${SRC} > ${TGT}',
> +update_outputs=True)
> +
> +
>  def net_config_header(bld):
>  if not os.path.exists(bld.env.NET_CONFIG):
>  bld.fatal('network configuraiton \'%s\' not found' %
> @@ -88,7 +107,14 @@ def options(opt):
>
>
>  def bsp_configure(conf, arch_bsp, mandatory=True):
> -ab = rtems.arch(arch_bsp) + '/' + rtems.bsp(arch_bsp)
> +conf.start_msg('Checking version')
> +version.load_rtems_version_header(conf, conf.env.RTEMS_VERSION, arch_bsp,
> +  conf.env.IFLAGS)
> +conf.env.RTEMS_NET_LEGACY_VERSION = version.string(conf)
> +conf.env.RTEMS_NET_LEGACY_MAJOR = version.version(conf)
> +conf.env.RTEMS_NET_LEGACY_REVISION = version.revision(conf)
> +conf.end_msg(conf.env.RTEMS_NET_LEGACY_VERSION)
> +ab = rtems.arch_bsp_name(arch_bsp)
>  includes = [
>  '.',
>  'include',
> @@ -125,9 +151,9 @@ def bsp_configure(conf, arch_bsp, mandatory=True):
>
>
>  def build(bld):
> -arch_bsp = bld.env.RTEMS_ARCH_BSP
> -ab = rtems.arch(arch_bsp) + '/' + rtems.bsp(arch_bsp)
> +ab = rtems.arch_bsp_name(bld.env.RTEMS_ARCH_BSP)
>
> +version_header(bld)
>  net_config_header(bld)
>
>  if ab in bsp_drivers.source:
> @@ -173,3 +199,6 @@ def build(bld):
>  bld.install_as(
>  os.path.join(bld.env.PREFIX, arch_inc_path, inc_dir, hname),
>  header)
> +bld.install_as(
> +os.path.join(bld.env.PREFIX, arch_inc_path, 'rtems',
> + 'rtems-net-legacy.h'), 
> 'include/rtems/rtems-net-legacy.h')
> diff --git a/rtems_waf b/rtems_waf
> index

[rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

2023-04-13 Thread chrisj

From: Chris Johns 

---
 include/rtems/rtems-net-legacy.h.in | 42 +
 netlegacy.py| 35 +---
 rtems_waf   |  2 +-
 3 files changed, 75 insertions(+), 4 deletions(-)
 create mode 100755 include/rtems/rtems-net-legacy.h.in

diff --git a/include/rtems/rtems-net-legacy.h.in 
b/include/rtems/rtems-net-legacy.h.in
new file mode 100755
index 000..a17ec21
--- /dev/null
+++ b/include/rtems/rtems-net-legacy.h.in
@@ -0,0 +1,42 @@
+/**
+ * @file
+ *
+ * @ingroup rtems_net_legacy
+ *
+ * @brief This file is generated
+ */
+
+/*
+ * Copyright (c) 2023. Chris Johns . All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ *notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ *notice, this list of conditions and the following disclaimer in the
+ *documentation and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ */
+
+#ifndef _RTEMS_NET_LGEACY_H_
+#define _RTEMS_NET_LEGACY_H_
+
+#define RTEMS_NET_LEGACY_VERSION  @RTEMS_NET_LEGACY_VERSION@
+
+#define RTEMS_NET_LEGACY_MAJOR@RTEMS_NET_LEGACY_MAJOR@
+#define RTEMS_NET_LEGACY_REVISION @RTEMS_NET_LEGACY_REVISION@
+
+#endif /* _RTEMS_NET_LGEACY_H_ */
diff --git a/netlegacy.py b/netlegacy.py
index 60775dc..9f27ffc 100644
--- a/netlegacy.py
+++ b/netlegacy.py
@@ -29,12 +29,31 @@
 import os
 import os.path
 
+from rtems_waf import git
 from rtems_waf import rtems
+from rtems_waf import version
 
 import bsp_drivers
 import netsources
 
 
+def version_header(bld):
+versions = {
+'RTEMS_NET_LEGACY_VERSION':
+'"' + bld.env.RTEMS_NET_LEGACY_VERSION + '"',
+'RTEMS_NET_LEGACY_MAJOR': bld.env.RTEMS_NET_LEGACY_MAJOR,
+'RTEMS_NET_LEGACY_REVISION':
+'"' + bld.env.RTEMS_NET_LEGACY_REVISION + '"',
+}
+sed = 'sed '
+for cfg in versions:
+sed += "-e 's/@%s@/%s/' " % (cfg, versions[cfg])
+bld(target='include/rtems/rtems-net-legacy.h',
+source='include/rtems/rtems-net-legacy.h.in',
+rule=sed + ' < ${SRC} > ${TGT}',
+update_outputs=True)
+
+
 def net_config_header(bld):
 if not os.path.exists(bld.env.NET_CONFIG):
 bld.fatal('network configuraiton \'%s\' not found' %
@@ -88,7 +107,14 @@ def options(opt):
 
 
 def bsp_configure(conf, arch_bsp, mandatory=True):
-ab = rtems.arch(arch_bsp) + '/' + rtems.bsp(arch_bsp)
+conf.start_msg('Checking version')
+version.load_rtems_version_header(conf, conf.env.RTEMS_VERSION, arch_bsp,
+  conf.env.IFLAGS)
+conf.env.RTEMS_NET_LEGACY_VERSION = version.string(conf)
+conf.env.RTEMS_NET_LEGACY_MAJOR = version.version(conf)
+conf.env.RTEMS_NET_LEGACY_REVISION = version.revision(conf)
+conf.end_msg(conf.env.RTEMS_NET_LEGACY_VERSION)
+ab = rtems.arch_bsp_name(arch_bsp)
 includes = [
 '.',
 'include',
@@ -125,9 +151,9 @@ def bsp_configure(conf, arch_bsp, mandatory=True):
 
 
 def build(bld):
-arch_bsp = bld.env.RTEMS_ARCH_BSP
-ab = rtems.arch(arch_bsp) + '/' + rtems.bsp(arch_bsp)
+ab = rtems.arch_bsp_name(bld.env.RTEMS_ARCH_BSP)
 
+version_header(bld)
 net_config_header(bld)
 
 if ab in bsp_drivers.source:
@@ -173,3 +199,6 @@ def build(bld):
 bld.install_as(
 os.path.join(bld.env.PREFIX, arch_inc_path, inc_dir, hname),
 header)
+bld.install_as(
+os.path.join(bld.env.PREFIX, arch_inc_path, 'rtems',
+ 'rtems-net-legacy.h'), 'include/rtems/rtems-net-legacy.h')
diff --git a/rtems_waf b/rtems_waf
index 1a118bb..2c15b90 16
--- a/rtems_waf
+++ b/rtems_waf
@@ -1 +1 @@
-Subproject commit 1a118bbcd52138dbdc3236e64bc23fd430a064b1
+Subproject commit 2c15b90de5c369aa78cd2252a50bba677e9b13f3
-- 
2.31.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

2023-04-13 Thread Chris Johns

On 13/4/2023 11:48 pm, Will wrote:
> This change is fine, but it also needs the packageconfig change to match. The
> thread from October has the full patch (title was "[PATCH v2] spec/pkgconfig:
> Allow builds to override headers"). This also needs a change to libbsd to
> account for this alteration, IIRC.

I have just found the v2 version of your patch:

 https://lists.rtems.org/pipermail/devel/2022-October/073629.html

I will push it with a change to the commit message to close the ticket I opened.

This patch being missed highlights how we need a merge request system.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

2023-04-13 Thread Chris Johns

On 14/4/2023 1:32 am, Joel Sherrill wrote:
> On Thu, Apr 13, 2023 at 8:49 AM Will  > wrote:
> 
> This change is fine, but it also needs the packageconfig change to match.
> The thread from October has the full patch (title was "[PATCH v2]
> spec/pkgconfig: Allow builds to override headers"). This also needs a 
> change
> to libbsd to account for this alteration, IIRC.

Yes it does and thanks for raising this. I will pick up your changes as well.

> This is OK but the use of -B added to the system header file and library 
> include
> paths. If we don't want to use -B any longer,

GCC says:

 -Bprefix

This option specifies where to find the executables, libraries,
include files, and data files of the compiler itself.

I think -isystem is the option we want. The documentation says:

  The -isystem and -idirafter options also mark the directory as a
  system directory, so that it gets the same special treatment that
  is applied to the standard system directories.

Ref: https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html#Directory-Options

> there is likely a system library include argument that is needed.

That is not an issue with the packages I am dealing with. In Makefile.inc the
include path is part of CPPFLAGS and not LDFLAGS.

> And -B had nothing to do with the spec file except

Ah yes I was wrong.

> that it also told gcc where
> it was since it added that base directory as a system directory.

The documentation would indicate it is a compiler path and the -isystem path is
a system include path. We support builds with the tools (ie compiler) in one
path and RTEMS headers in another.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

ESA Mission Juice Launch

2023-04-13 Thread Joel Sherrill

 Hi

The JUICE mission was scheduled to launch today but unfortunately, there
was a delay on the launch of the ESA Juice mission this morning due to
lightning. But on a positive note, it means that we all didn't miss it. :)
It is scheduled for Friday at 8:14 a.m. ET.

"After JUICE arrives at Jupiter in July 2031, the spacecraft will spend
about three and a half years orbiting the gas giant and conducting flybys
of three of its moons: Ganymede, Callisto and Europa. Toward the end of the
mission, Juice will focus solely on orbiting Ganymede, making it the first
spacecraft to ever orbit a moon in the outer solar system."

AFAIK this mission includes at least RTEMS based instruments and Data
Processing Unit (DPU). If anyone has more details on the use of RTEMS on
this mission, please share.

https://flightsoftware.jhuapl.edu/files/2016/Day-3/Day-3-13-Hellstrom.pdf

More general info on the mission

https://www.bbc.com/news/science-environment-65254502

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

2023-04-13 Thread Joel Sherrill

On Thu, Apr 13, 2023 at 8:49 AM Will  wrote:

> This change is fine, but it also needs the packageconfig change to match.
> The thread from October has the full patch (title was "[PATCH v2]
> spec/pkgconfig: Allow builds to override headers"). This also needs a
> change to libbsd to account for this alteration, IIRC.
>

This is OK but the use of -B added to the system header file and library
include paths. If we don't want to use -B any longer, there is likely a
system library include argument that is needed.

And -B had nothing to do with the spec file except that it also told gcc
where it was since it added that base directory as a system directory.

--joel


> Kinsey
>
> On Wed, Apr 12, 2023 at 5:20 PM  wrote:
>
>> From: Chris Johns 
>>
>> - Export the BSP include path as a system include path so the order
>>   of options on an application compiler command line does not matter.
>>
>> Closes #4896
>> ---
>>  spec/build/bsps/makecustom.yml | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/spec/build/bsps/makecustom.yml
>> b/spec/build/bsps/makecustom.yml
>> index 139629b597..c00240595e 100644
>> --- a/spec/build/bsps/makecustom.yml
>> +++ b/spec/build/bsps/makecustom.yml
>> @@ -2,7 +2,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
>>  build-type: config-file
>>  content: |
>>include $$(RTEMS_ROOT)/make/custom/default.cfg
>> -  CPU_DEFINES = -I$$(exec_prefix)/$$(RTEMS_BSP)/lib/include
>> +  CPU_DEFINES = -isystem $$(exec_prefix)/$$(RTEMS_BSP)/lib/include
>>CPU_CFLAGS = ${ABI_FLAGS}
>>CFLAGS_OPTIMIZE_V = ${OPTIMIZATION_FLAGS}
>>LDFLAGS = -B$$(exec_prefix)/$$(RTEMS_BSP)/lib ${PKGCONFIG_LDFLAGS}
>> --
>> 2.37.1
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

2023-04-13 Thread Will

This change is fine, but it also needs the packageconfig change to match.
The thread from October has the full patch (title was "[PATCH v2]
spec/pkgconfig: Allow builds to override headers"). This also needs a
change to libbsd to account for this alteration, IIRC.

Kinsey

On Wed, Apr 12, 2023 at 5:20 PM  wrote:

> From: Chris Johns 
>
> - Export the BSP include path as a system include path so the order
>   of options on an application compiler command line does not matter.
>
> Closes #4896
> ---
>  spec/build/bsps/makecustom.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/spec/build/bsps/makecustom.yml
> b/spec/build/bsps/makecustom.yml
> index 139629b597..c00240595e 100644
> --- a/spec/build/bsps/makecustom.yml
> +++ b/spec/build/bsps/makecustom.yml
> @@ -2,7 +2,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
>  build-type: config-file
>  content: |
>include $$(RTEMS_ROOT)/make/custom/default.cfg
> -  CPU_DEFINES = -I$$(exec_prefix)/$$(RTEMS_BSP)/lib/include
> +  CPU_DEFINES = -isystem $$(exec_prefix)/$$(RTEMS_BSP)/lib/include
>CPU_CFLAGS = ${ABI_FLAGS}
>CFLAGS_OPTIMIZE_V = ${OPTIMIZATION_FLAGS}
>LDFLAGS = -B$$(exec_prefix)/$$(RTEMS_BSP)/lib ${PKGCONFIG_LDFLAGS}
> --
> 2.37.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

AW: [PATCH 02/18] ptpd: Add VERSION file

2023-04-13 Thread Gabriel.Moyano

> > ---
> >   freebsd/contrib/ptpd/VERSION | 11 +++
> >   1 file changed, 11 insertions(+)
> >   create mode 100644 freebsd/contrib/ptpd/VERSION
> >
> > diff --git a/freebsd/contrib/ptpd/VERSION
> > b/freebsd/contrib/ptpd/VERSION new file mode 100644 index
> > ..4c95e563
> > --- /dev/null
> > +++ b/freebsd/contrib/ptpd/VERSION
> > @@ -0,0 +1,11 @@
> > +Import from:
> > +
> > +https://github.com/ptpd/ptpd
> > +
> > +Commit:
> > +
> > +1ec9e650b03e6bd75dd3179fb5f09862ebdc54bf
> > +
> > +Date:
> > +
> > +Wed Sep 4 20:12:53 2019 -0400
> 
> The freebsd directory mirrors the FreeBSD source tree. Since the ptpd is not
> included in FreeBSD it should be placed outside the freebsd directory, for
> example ptpd at the top level or rtemsbsd/ptpd.
> 
Sure, I can move the files to rtemsbsd/ptpd. But before submitting the patches 
again, is there any other change suggested?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 02/18] ptpd: Add VERSION file

2023-04-13 Thread Sebastian Huber


On 12.04.23 15:54, Gabriel Moyano wrote:

---
  freebsd/contrib/ptpd/VERSION | 11 +++
  1 file changed, 11 insertions(+)
  create mode 100644 freebsd/contrib/ptpd/VERSION

diff --git a/freebsd/contrib/ptpd/VERSION b/freebsd/contrib/ptpd/VERSION
new file mode 100644
index ..4c95e563
--- /dev/null
+++ b/freebsd/contrib/ptpd/VERSION
@@ -0,0 +1,11 @@
+Import from:
+
+https://github.com/ptpd/ptpd
+
+Commit:
+
+1ec9e650b03e6bd75dd3179fb5f09862ebdc54bf
+
+Date:
+
+Wed Sep 4 20:12:53 2019 -0400


The freebsd directory mirrors the FreeBSD source tree. Since the ptpd is 
not included in FreeBSD it should be placed outside the freebsd 
directory, for example ptpd at the top level or rtemsbsd/ptpd.


--
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-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

AW: [PATCH 00/18] Port PTPd to rtems-libbsd

2023-04-13 Thread Gabriel.Moyano

> On 12/4/2023 11:54 pm, Gabriel Moyano wrote:
> > These commits are for porting PTPd to rtems-libbsd and are based on the
> master branch.
> >
> > This work is a joint effort with Chris Johns, which we started some time
> ago.
> > Originally, we wanted to port some of the commits to PTPd upstream but
> unfortunately the project is no longer maintained (our pull request has been
> open for more than a year).
> > For this reason, we decided to add PTPd files as contrib.
> > In fact, this is the first commit.
> >
> > One important feature introduced to PTPd is the support for kqueue,
> which was done by Chris.
> > Also, a new test for running a PTPd instance was added to the test suit.
> >
> > I'm happy to hear feedback from you.
> 
> Thank for you for all the work I know has gone into getting this package
> together. It has been a journey. It is great to see the work reach this 
> finished
> level ready to merge.

Thanks you too.

> Is this for the master, 6-freebsd-12 or both branches of libbsd?
> 

It is for the master, once approved I'll create the one for 6-freebsd-12. I 
understand that there will be some changes needed.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

Re: [rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

[rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

ESA Mission Juice Launch

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

AW: [PATCH 02/18] ptpd: Add VERSION file

Re: [PATCH 02/18] ptpd: Add VERSION file

AW: [PATCH 00/18] Port PTPd to rtems-libbsd

11 matches

Site Navigation

Mail list logo

Footer information