On 10/11/2022 01:30, Chris Johns wrote:
The first is the maintenance of embedded the version numbers in the
documentation. If we can avoid doing that the work per release or dot
release is less.
We could use a simple search and replace for this. Searching for
'rtems[0-9]' shows a couple of sp
Hi Kinsey,
> On Thu, 2022-11-10 at 07:55 -0600, Kinsey Moore wrote:
>
> Hi Padmarao,
> More compatibles can be added later if necessary to both the device
> tree in RTEMS and the driver in RTEMS-LibBSD, but I don't see the
> need for either at the moment since the ethernet portion of the
> device
On 11/11/22 8:36 am, Kinsey Moore wrote:
> This should be covered by COPYING.rtemslwip. I would say it isn't worth
> putting
> it in the intentionally empty files.
Agreed. Copyright of "empty" does not make sense.
Chris
___
devel mailing list
devel@rte
From: Chris Johns
Close #4756
---
common/waf.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/common/waf.py b/common/waf.py
index 8584f88..0bd166a 100644
--- a/common/waf.py
+++ b/common/waf.py
@@ -275,21 +275,21 @@ def cmd_configure(ctx):
if ctx.options.singleht
From: Chris Johns
Close #4755
---
common/waf.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/common/waf.py b/common/waf.py
index 8584f88..0bd166a 100644
--- a/common/waf.py
+++ b/common/waf.py
@@ -275,21 +275,21 @@ def cmd_configure(ctx):
if ctx.options.singleht
This should be covered by COPYING.rtemslwip. I would say it isn't worth
putting it in the intentionally empty files.
On Thu, Nov 10, 2022 at 2:22 PM Vijay Kumar Banerjee
wrote:
> Looks good to me.
>
> Do we need copyright statements for these files?
>
> On Wed, Nov 9, 2022 at 9:49 PM Kinsey Moor
This adds support for the CFC-400X BSP including an option to select
SGMII instead of the default RGMII PHY interface and adds a way for
ZynqMP BSPs to provide additional configuration via lwipbspopts.h.
---
.../aarch64/xilinx_zynqmp_lp64_cfc400x.json | 11
.../contrib/ports/xilinx/netif/xe
OK.
Thanks
Chris
On 10/11/22 4:01 am, Kinsey Moore wrote:
> ---
> cpukit/include/rtems/rtems-fdt.h | 24 +++-
> 1 file changed, 15 insertions(+), 9 deletions(-)
>
> diff --git a/cpukit/include/rtems/rtems-fdt.h
> b/cpukit/include/rtems/rtems-fdt.h
> index 3919593582..18e043
Looks good to me.
Do we need copyright statements for these files?
On Wed, Nov 9, 2022 at 9:49 PM Kinsey Moore wrote:
>
> ---
> rtemslwip/bsd_compat_include/arpa/nameser.h | 1 +
> rtemslwip/bsd_compat_include/machine/rtems-bsd-kernel-space.h | 1 +
> rtemslwip/bsd_compat_incl
Thanks for the patch. The v2 looks good. Tested the build with beagleboneblack
On Wed, Nov 9, 2022 at 9:33 PM Kinsey Moore wrote:
>
> This moves all BSP-specific information out of lwip.py and into JSON
> descriptions of the files required to compile the drivers for each BSP.
>
> Note that file-i
Hi Padmarao,
More compatibles can be added later if necessary to both the device tree in
RTEMS and the driver in RTEMS-LibBSD, but I don't see the need for either
at the moment since the ethernet portion of the device tree is intended to
be used with RTEMS-LibBSD directly. As far as the driver in 6
Hi Kinsey,
The ethernet compatible "cdns,gem" is mentioned in the device tree,
even I used same for PolarFire SoC BSP but later realised that common
compatible for the candence GEM is "cdns,macb" used in U-Boot and
Linux.
Can we go with compatible "cdns,gem"? or will we update with
"cdns,macb" la
On 10/11/22 3:40 pm, Gedare Bloom wrote:
> looks fine. i'm not sure where
> + "review": ("Gerrit Code Review",
> "https://review.rtems.org/";),
> came from, but I see it in before too.
It came from the initial work Amar did in moving us to the RST format.
There is no service provided
13 matches
Mail list logo
