Unsubscribe

Franck BUCHERON franck.bucheron at wanadoo.fr
Fri Feb 28 15:53:52 UTC 2020


 
Envoyé depuis l'application Mail Orange
----------------
Le 28/02/2020, à 14:50, devel-request at rtems.org a écrit :

Send devel mailing list submissions to
	devel at rtems.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.rtems.org/mailman/listinfo/devel
or, via email, send a message with subject or body 'help' to
	devel-request at rtems.org

You can reach the person managing the list at
	devel-owner at rtems.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of devel digest..."


Today's Topics:

   1. Re: Suggestion (Christian Mauderer)
   2. Re: [Project #3860] (Christian Mauderer)
   3. Re: [PATCH 27/27] dtc: Update VERSION (Joel Sherrill)
   4. Re: [PATCH 27/27] dtc: Update VERSION (Sebastian Huber)
   5. Re: Link issue on xilinx_zynq_a9_qemu BSP on rtems-libbsd
      head (Alan Cudmore)


----------------------------------------------------------------------

Message: 1
Date: Fri, 28 Feb 2020 13:10:20 +0100
From: Christian Mauderer <christian.mauderer at embedded-brains.de>
To: Anmol Mishra <anmol.j2020 at gmail.com>, devel at rtems.org
Subject: Re: Suggestion
Message-ID: <2308b10c-8eb6-3003-8cdc-87704c983e54 at embedded-brains.de>
Content-Type: text/plain; charset=utf-8

Hello Anmol,

On 28/02/2020 10:49, Anmol Mishra wrote:
> I can see python2 code being used. And as of 2020 python2 has been
> depreciated but I assume everyone is aware of that. Is there any active
> plan to shift the codebase. I am open to discussion for this. 

We have the problem that some long living distributions (like CentOS 7)
still only have python2 in the default repositories. So till they run
out of support (year 2024 for CentOS 7) we will have to write our code
in a way that it works with python2 and 3 for everything that is daily
use for a RTEMS user.

We currently have the discussion for some special maintenance tools
whether they can be python3 only.

So as a summary: If you find any tool that works with python2 but not
with python3 it should definitively be updated to work with both
versions. Patches are welcome.

Best regards

Christian

> 
> Regards
> Anmol
> 
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
> 

-- 
--------------------------------------------
embedded brains GmbH
Herr Christian Mauderer
Dornierstr. 4
D-82178 Puchheim
Germany
email: christian.mauderer at embedded-brains.de
Phone: +49-89-18 94 741 - 18
Fax:   +49-89-18 94 741 - 08
PGP: Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.


------------------------------

Message: 2
Date: Fri, 28 Feb 2020 13:34:48 +0100
From: Christian Mauderer <christian.mauderer at embedded-brains.de>
To: Anmol Mishra <anmol.j2020 at gmail.com>, chrisj at rtems.org,
	devel at rtems.org
Subject: Re: [Project #3860]
Message-ID: <d857c60a-922b-1f3f-c065-edccedfbec99 at embedded-brains.de>
Content-Type: text/plain; charset=utf-8

Hello Anmol,

On 28/02/2020 10:31, Anmol Mishra wrote:
> Hello,
> I was going through the list of potential projects for GSoC 2020, I love
> working with automation tools and "Code Formatting and Style Check for
> RTEMS score" looks exciting to me. I saw you edited the wiki and the
> owner was not mentioned so pinging you for the same.

I'm not sure whether we already assigned someone. But that is a topic
that could be handled by multiple mentors. So your best bet is to ask on
the list.

> I have read the requirements and hurdles, I have a question that
> 1. "Is there any tool/procedure currently being considered as an option?"

Not as far as I'm concerned. You might want to have a look at the wiki.
I think there have been some notes for code formatters a few years back.

> 2. "What is the timeframe I should look in the mail archive like the
> past 3 months?"

That topic was created during a recent discussion regarding style
checking for Python. It can only be a few weeks now. But there haven't
been much details about it.

Best regards

Christian

> 
> It goes without saying how much this means to me. I will be submitting 2
> project proposals and don't want to waste time and start with draft
> proposal asap. Looking?forward to hearing from you.
> 
> Regards
> Anmol
> 
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
> 

-- 
--------------------------------------------
embedded brains GmbH
Herr Christian Mauderer
Dornierstr. 4
D-82178 Puchheim
Germany
email: christian.mauderer at embedded-brains.de
Phone: +49-89-18 94 741 - 18
Fax:   +49-89-18 94 741 - 08
PGP: Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.


------------------------------

Message: 3
Date: Fri, 28 Feb 2020 06:57:55 -0600
From: Joel Sherrill <joel at rtems.org>
To: Sebastian Huber <sebastian.huber at embedded-brains.de>
Cc: RTEMS Devel <rtems-devel at rtems.org>
Subject: Re: [PATCH 27/27] dtc: Update VERSION
Message-ID:
	<CAF9ehCVQ9JUctE0O3ZgtNAtkUYWVPz0C97tTxz-QT3OvF96EFw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I'm not opposed to this. I noticed a local uncommitted patch I posted a
while
back to bump dtc in rtems-tools.  What about that as well?


On Fri, Feb 28, 2020, 12:52 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> ---
>  cpukit/dtc/VERSION | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/cpukit/dtc/VERSION b/cpukit/dtc/VERSION
> index fa27eb5c8e..a6f7720958 100644
> --- a/cpukit/dtc/VERSION
> +++ b/cpukit/dtc/VERSION
> @@ -4,15 +4,15 @@ git://git.kernel.org/pub/scm/utils/dtc/dtc.git
>
>  Commit:
>
> -c12b2b0c20eb8fbe1a22065f1d5f0f155ab56b0a
> +0f61c72dedc4bf11cd19a78fc36a7bde99d653e0
>
>  Date:
>
> -Thu Jul 19 08:19:43 2018 +0200
> +Thu Feb 20 14:45:57 2020 -0700
>
>  Commands to generate update patches:
>
> -git format-patch c12b2b0c20eb8fbe1a22065f1d5f0f155ab56b0a --
> libfdt/fdt_addresses.c libfdt/fdt.c libfdt/fdt_empty_tree.c libfdt/fdt.h
> libfdt/fdt_ro.c libfdt/fdt_rw.c libfdt/fdt_strerror.c libfdt/fdt_sw.c
> libfdt/fdt_wip.c libfdt/libfdt_env.h libfdt/libfdt.h
> libfdt/libfdt_internal.h libfdt/TODO
> +git format-patch 0f61c72dedc4bf11cd19a78fc36a7bde99d653e0 --
> libfdt/fdt_addresses.c libfdt/fdt.c libfdt/fdt_empty_tree.c libfdt/fdt.h
> libfdt/fdt_ro.c libfdt/fdt_rw.c libfdt/fdt_strerror.c libfdt/fdt_sw.c
> libfdt/fdt_wip.c libfdt/libfdt_env.h libfdt/libfdt.h
> libfdt/libfdt_internal.h libfdt/TODO
>  sed -i 's%/libfdt/fdt.h%/cpukit/include/fdt.h%g' 00*
>  sed -i 's%/libfdt/libfdt.h%/cpukit/include/libfdt.h%g' 00*
>  sed -i 's%/libfdt/libfdt_env.h%/cpukit/include/libfdt_env.h%g' 00*
> --
> 2.16.4
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200228/303c5c1a/attachment-0001.html>

------------------------------

Message: 4
Date: Fri, 28 Feb 2020 14:00:28 +0100
From: Sebastian Huber <sebastian.huber at embedded-brains.de>
To: joel at rtems.org
Cc: RTEMS Devel <rtems-devel at rtems.org>
Subject: Re: [PATCH 27/27] dtc: Update VERSION
Message-ID: <065f6bcc-2b8a-b9cc-211a-3765210b10d4 at embedded-brains.de>
Content-Type: text/plain; charset=utf-8; format=flowed

On 28/02/2020 13:57, Joel Sherrill wrote:
> I'm not opposed to this. I noticed a local uncommitted patch I posted a 
> while
> back to bump dtc in rtems-tools.? What about that as well?

It probably doesn't hurt to update this.

I updated the dtc code in RTEMS just because it was mentioned as an 
example for third-party code without SPDX license identifiers.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.


------------------------------

Message: 5
Date: Fri, 28 Feb 2020 08:50:24 -0500
From: Alan Cudmore <alan.cudmore at gmail.com>
To: Sebastian Huber <sebastian.huber at embedded-brains.de>
Cc: "rtems-devel at rtems.org" <rtems-devel at rtems.org>
Subject: Re: Link issue on xilinx_zynq_a9_qemu BSP on rtems-libbsd
	head
Message-ID:
	<CAJrjN70dmEVvRiAniZ5L=hrVw+MGbBjZJx7C0mV5qrpgk5SAdw at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

I had logged the verbose output from waf building the testsuite, but I
missed a couple of linker options in my makefile. It links now.
Is there a standalone rtems-libbsd example with a waf script or makefile?
Thank your for your quick response,
Alan

On Fri, Feb 28, 2020 at 1:25 AM Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
>
> On 28/02/2020 04:40, Alan Cudmore wrote:
> > Hi Lou,
> > Did you ever solve this problem?
> > I just tried linking an out of tree program for the beaglebone black
> > BSP and have the same undefined symbols. The testsuite links correctly
> > and the symbols are in the testsuite binaries, but not in libbsd.a
>
> For libbsd it is required that you link with the section garbage
> collection enabled: -Wl,--gc-sections
>
> This is how the tests are linked. If you omit the -Wl,--gc-sections in
> your application you do something which is not tested.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.


------------------------------

Subject: Digest Footer

_______________________________________________
devel mailing list
devel at rtems.org
http://lists.rtems.org/mailman/listinfo/devel

------------------------------

End of devel Digest, Vol 99, Issue 204
**************************************


More information about the devel mailing list