Re: RFC: Exceptions to PEP-8 Adoption for RTEMS Tools

On 19/3/20 7:06 am, Christian Mauderer wrote: > Hello Amar, > > On 18/03/2020 19:24, Amar Takhar wrote: >> The only one I would like to propose is the 80 character limit. This should >> be >> moved to something more reasonable such as 120. >> >> Code comments should remain below 80 however. >>

Re: Improve the Raspberry Pi BSP

I will create a new thread soon. Thank you Denil. On Wed, 18 Mar, 2020, 11:56 PM Gedare Bloom, wrote: > On Wed, Mar 18, 2020 at 11:12 AM Denil Verghese > wrote: > > > > > > > > On Wed, 18 Mar, 2020, 9:03 PM Gedare Bloom, wrote: > >> > >> On Wed, Mar 18, 2020 at 8:41 AM Denil Verghese >

Re: Improve the Raspberry Pi BSP

On Wed, 18 Mar, 2020, 10:55 PM Alan Cudmore, wrote: > While, I would like to see additional improvement to the Raspberry Pi > BSPs, I don't think I have the time to serve as a mentor this year. I > am sure I could not keep up with the daily communication that is > required for a successful GSoC

Re: [rtems-examples PATCH v2 1/2] Update rtems_waf

Both these patches are fine to push. Vijay, please push once your access has been sorted out. I should highlight I am OK with the approach taken in the examples repo, that is not building something if the dependent tool is not found rather than raising an error. Thanks Chris On 18/3/20 8:43 pm,

Re: GSoC 2020 memory protection project initial draft.

Oh sorry, I have rectified that now. On Wed, Mar 18, 2020 at 11:34 PM Gedare Bloom wrote: > Provide edit access so I can add comments / suggestions. > > On Tue, Mar 17, 2020 at 11:41 PM Utkarsh Rai > wrote: > >> Hi, I have prepared my initial draft for the project and look forward to >> your

Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100

On Wed, Mar 18, 2020 at 2:38 PM Heinz Junkes wrote: > Hello, Mritunjay, > > I will contact you tomorrow during the day (European time). We have here > institute closings because of Corona Virus etc.. > > It's great that you've come this far. I can also provide you with an > MVME6100 remotely so

Maintainers of rtems-littlevgl package

Hi everyone, I'm pleased to announce that the rtems-littlevgl package will be maintained (officially) by Christian Mauderer and Vijay Kumar Bannerjee. Christian/Vijay, please add a README file to the rtems-littlevgl package and include some details about the role of that repo in RTEMS, and with

ANN: New Maintainer Vijay Kumar Bannerjee

Hello all, I'm pleased to announce Vijay Kumar Bannerjee is being added as a maintainer for the "beagle" BSPs and as write-after-approval elsewhere. Vijay was a GSoC Student in 2018 and 2019, and he has been an energetic and enthusiastic member of the community since his first student experience.

Re: RFC: Exceptions to PEP-8 Adoption for RTEMS Tools

Hello Amar, On 18/03/2020 19:24, Amar Takhar wrote: > The only one I would like to propose is the 80 character limit. This should > be > moved to something more reasonable such as 120. > > Code comments should remain below 80 however. > I'm not a big fan of long lines (reason further below)

Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100

Hello, Mritunjay, I will contact you tomorrow during the day (European time). We have here institute closings because of Corona Virus etc.. It's great that you've come this far. I can also provide you with an MVME6100 remotely so you can get a feeling for target development. Yes, I have

Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100

Thank you so much for the feedback. I will research more on the targets that can run with the simulator and would like to tell you that looking at https://github.com/hjunkes/epicsBaseOwnPlayground/tree/7.0, I feel that @Heinz Junkes is already working on libbsd for RTEMS-MVME2500 and I would like

Re: Improve the Raspberry Pi BSP

On Wed, Mar 18, 2020 at 11:12 AM Denil Verghese wrote: > > > > On Wed, 18 Mar, 2020, 9:03 PM Gedare Bloom, wrote: >> >> On Wed, Mar 18, 2020 at 8:41 AM Denil Verghese wrote: >> > >> > >> > >> > On Wed, 18 Mar, 2020, 7:43 PM Alan Cudmore, wrote: >> >> >> >> This is probably not a comprehensive

Re: RFC: Exceptions to PEP-8 Adoption for RTEMS Tools

The only one I would like to propose is the 80 character limit. This should be moved to something more reasonable such as 120. Code comments should remain below 80 however. Python itself has not followed this rule for a long time you can see many lines over 80 in the Python source itself.

Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100

On Wed, Mar 18, 2020 at 11:40 AM Mritunjay Sharma wrote: > > Hi everyone, > > As a part of working on ticket #3835 (BSP Buildset for EPICS), this is to > inform the community that after a lot of research, help from RTEMS and EPICS > community and >

Re: GSoC 2020 memory protection project initial draft.

Provide edit access so I can add comments / suggestions. On Tue, Mar 17, 2020 at 11:41 PM Utkarsh Rai wrote: > Hi, I have prepared my initial draft for the project and look forward to > your feedback on the same. > I have also added this to the GSoC tracking page. > GSOC2020_

Successfully built EPICS 7 with RTEMS 5 for mvme6100

Hi everyone, As a part of working on ticket #3835 (BSP Buildset for EPICS), this is to inform the community that after a lot of research, help from RTEMS and EPICS community and https://epics.mpg.de/index.php?n=Software.EPICSRTEMS?userlang=en, I was able to build EPICS 7 for RTEMS 5 for mvme6100

RFC: Exceptions to PEP-8 Adoption for RTEMS Tools

Hello all, Sebastian has proposed some Python development guidelines for the SWEng book, which is great and I'm even going to steal some of his words here. I want to open the discussion for comments and requests for changes to one specific point: Python Coding Style. I'm specifically interested

Re: Improve the Raspberry Pi BSP

While, I would like to see additional improvement to the Raspberry Pi BSPs, I don't think I have the time to serve as a mentor this year. I am sure I could not keep up with the daily communication that is required for a successful GSoC project. Alan On Wed, Mar 18, 2020 at 1:12 PM Denil Verghese

Re: [PATCH 2/2] Add a message to run 'pytest' to run rest of test suite.

On Wed, Mar 18, 2020 at 9:20 AM Amar Takhar wrote: > > On 2020-03-18 16:16 +1100, Chris Johns wrote: > > > > Are these plugins extra dependencies or are they part of our test code? > > Dependencies on pytest but we can include them in the test suite just fine. > This is what I usually do. Most

Re: Improve the Raspberry Pi BSP

On Wed, 18 Mar, 2020, 9:03 PM Gedare Bloom, wrote: > On Wed, Mar 18, 2020 at 8:41 AM Denil Verghese wrote: > > > > > > > > On Wed, 18 Mar, 2020, 7:43 PM Alan Cudmore, > wrote: > >> > >> This is probably not a comprehensive list, but currently all models > except the Pi 4 are working thanks to

Re: [rtems-libbsd commit] nfsclient: Use a system event for RPC

On 18/03/2020 16:47, Joel Sherrill wrote: Is this the same as the NFS client for the legacy stack? Probably yes. In the libbsd I had to rewrite some parts to use kqueue() instead of events in some parts. ___ devel mailing list devel@rtems.org

[PATCH] c-user: Use new template for feature config opts

Try to bring all descriptions up to date. Add cross-references to several options. Update #3900. --- c-user/config/bdbuf.rst | 21 ++- c-user/config/classic-init-task.rst | 35 ++-- c-user/config/device-driver.rst | 278 +++--

Re: [rtems-libbsd commit] nfsclient: Use a system event for RPC

Is this the same as the NFS client for the legacy stack? On Wed, Mar 18, 2020, 2:27 AM Sebastian Huber wrote: > Module:rtems-libbsd > Branch:5-freebsd-12 > Commit:039afd9816122fc52f77966dc78430e009aa220c > Changeset: >

Re: Re: Improve the Raspberry Pi BSP

On Wed, Mar 18, 2020 at 8:41 AM Denil Verghese wrote: > > > > On Wed, 18 Mar, 2020, 7:43 PM Alan Cudmore, wrote: >> >> This is probably not a comprehensive list, but currently all models except >> the Pi 4 are working thanks to Niteesh’s work on the uart for the Pi 3 and >> Zero W. >> >> >> >>

Re: [PATCH 2/2] Add a message to run 'pytest' to run rest of test suite.

On 2020-03-18 16:16 +1100, Chris Johns wrote: > > Are these plugins extra dependencies or are they part of our test code? Dependencies on pytest but we can include them in the test suite just fine. This is what I usually do. Most of them are a single Python file. Amar.

Re: Re: Improve the Raspberry Pi BSP

On Wed, 18 Mar, 2020, 7:43 PM Alan Cudmore, wrote: > This is probably not a comprehensive list, but currently all models except > the Pi 4 are working thanks to Niteesh’s work on the uart for the Pi 3 and > Zero W. > > > > I believe there is some support for GPIO, and I2C. > > I’m not sure about

RE: Re: Improve the Raspberry Pi BSP

This is probably not a comprehensive list, but currently all models except the Pi 4 are working thanks to Niteesh’s work on the uart for the Pi 3 and Zero W. I believe there is some support for GPIO, and I2C.I’m not sure about the state of SPI.There is also support for the graphics console, but I

[PATCH v1 06/16] Py2/3 compliant tools/gdb/python/percpu.py

From: Anmol Mishra --- tools/gdb/python/percpu.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tools/gdb/python/percpu.py b/tools/gdb/python/percpu.py index 991bdf8..fb2d6d8 100644 --- a/tools/gdb/python/percpu.py +++ b/tools/gdb/python/percpu.py @@ -31,9 +31,11 @@ #

[PATCH v1 04/16] Py2/3 compliant tools/gdb/python/rtems.py

From: Anmol Mishra --- tools/gdb/python/rtems.py | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/tools/gdb/python/rtems.py b/tools/gdb/python/rtems.py index a097797..43232a6 100644 --- a/tools/gdb/python/rtems.py +++ b/tools/gdb/python/rtems.py @@ -31,15

[PATCH v1 02/16] Py2/3 compliant tools/gdb/python/pretty.py

From: Anmol Mishra --- tools/gdb/python/pretty.py | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/tools/gdb/python/pretty.py b/tools/gdb/python/pretty.py index 3cbe052..302dc2f 100644 --- a/tools/gdb/python/pretty.py +++ b/tools/gdb/python/pretty.py @@ -30,12

[PATCH v1 09/16] Py2/3 compliant tools/gdb/python/supercore.py

From: Anmol Mishra --- tools/gdb/python/supercore.py | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tools/gdb/python/supercore.py b/tools/gdb/python/supercore.py index 318ebb7..dd1420e 100644 --- a/tools/gdb/python/supercore.py +++ b/tools/gdb/python/supercore.py @@

[PATCH v1 11/16] Py2/3 compliant tools/gdb/python/classic.py

From: Anmol Mishra --- tools/gdb/python/classic.py | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/tools/gdb/python/classic.py b/tools/gdb/python/classic.py index b5aacf8..494eaea 100644 --- a/tools/gdb/python/classic.py +++

[PATCH v1 03/16] Py2/3 compliant tools/gdb/python/mutex.py

From: Anmol Mishra --- tools/gdb/python/mutex.py | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tools/gdb/python/mutex.py b/tools/gdb/python/mutex.py index 17f1900..eaae1ac 100644 --- a/tools/gdb/python/mutex.py +++ b/tools/gdb/python/mutex.py @@ -31,11 +31,13 @@ #

[PATCH v1 05/16] Py2/3 compliant tools/gdb/python/main.py

From: Anmol Mishra --- tools/gdb/python/main.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/gdb/python/main.py b/tools/gdb/python/main.py index 6fb7c54..945fb69 100644 --- a/tools/gdb/python/main.py +++ b/tools/gdb/python/main.py @@ -3,9 +3,11 @@ # # main

[PATCH v1 01/16] Py2/3 compliant tools/gdb/python

From: Anmol Mishra --- tools/gdb/python/__init__.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/gdb/python/__init__.py b/tools/gdb/python/__init__.py index 0ea5fb2..dfbe6ba 100644 --- a/tools/gdb/python/__init__.py +++ b/tools/gdb/python/__init__.py @@ -27,8

[PATCH v1 07/16] Py2/3 compliant tools/gdb/python/sparc.py

From: Anmol Mishra --- tools/gdb/python/sparc.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/gdb/python/sparc.py b/tools/gdb/python/sparc.py index 38f19b7..4879266 100644 --- a/tools/gdb/python/sparc.py +++ b/tools/gdb/python/sparc.py @@ -2,7 +2,10 @@ # RTEMS

[PATCH v1 12/16] Py2/3 compliant tools/gdb/python/heaps.py

From: Anmol Mishra --- tools/gdb/python/heaps.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/gdb/python/heaps.py b/tools/gdb/python/heaps.py index 14238e3..274942e 100644 --- a/tools/gdb/python/heaps.py +++ b/tools/gdb/python/heaps.py @@ -31,6 +31,8 @@ # RTEMS heap # +from

[PATCH v1 15/16] Py2/3 compliant tools/gdb/python/classic_printer.py

From: Anmol Mishra --- tools/gdb/python/classic_printer.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/gdb/python/classic_printer.py b/tools/gdb/python/classic_printer.py index 86e0eeb..121edc8 100644 --- a/tools/gdb/python/classic_printer.py +++

[PATCH v1 08/16] Py2/3 compliant tools/gdb/python/threads.py

From: Anmol Mishra --- tools/gdb/python/threads.py | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/tools/gdb/python/threads.py b/tools/gdb/python/threads.py index 690f77f..d050acc 100644 --- a/tools/gdb/python/threads.py +++ b/tools/gdb/python/threads.py @@

[PATCH v1 14/16] Py2/3 compliant tools/gdb/python/helper.py

From: Anmol Mishra --- tools/gdb/python/helper.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/gdb/python/helper.py b/tools/gdb/python/helper.py index e9fe2f8..ac7c944 100644 --- a/tools/gdb/python/helper.py +++ b/tools/gdb/python/helper.py @@ -30,6 +30,8 @@ # RTEMS GDB support

[PATCH v1 16/16] Py2/3 compliant tools/gdb/python/supercore_printer.py

From: Anmol Mishra --- tools/gdb/python/supercore_printer.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/gdb/python/supercore_printer.py b/tools/gdb/python/supercore_printer.py index 61241e3..d144b40 100644 --- a/tools/gdb/python/supercore_printer.py +++

[PATCH v1 13/16] Py2/3 compliant tools/gdb/python/rbtrees.py

From: Anmol Mishra --- tools/gdb/python/rbtrees.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/gdb/python/rbtrees.py b/tools/gdb/python/rbtrees.py index 2e4c9e7..ace598c 100644 --- a/tools/gdb/python/rbtrees.py +++ b/tools/gdb/python/rbtrees.py @@ -31,6 +31,8

[PATCH v1 10/16] Py2/3 compliant tools/gdb/python/watchdog.py

From: Anmol Mishra --- tools/gdb/python/watchdog.py | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tools/gdb/python/watchdog.py b/tools/gdb/python/watchdog.py index 6a80421..b758e11 100644 --- a/tools/gdb/python/watchdog.py +++ b/tools/gdb/python/watchdog.py @@

[rtems-examples PATCH v2 2/2] filesystem: Add checks for rtems-bin2c

--- file_io/crc/wscript| 23 --- filesystem/fat_ramdisk/wscript | 18 +- 2 files changed, 21 insertions(+), 20 deletions(-) diff --git a/file_io/crc/wscript b/file_io/crc/wscript index 531da20..45384a9 100644 --- a/file_io/crc/wscript +++

[rtems-examples PATCH v2 1/2] Update rtems_waf

--- rtems_waf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtems_waf b/rtems_waf index e7a75df..ad08908 16 --- a/rtems_waf +++ b/rtems_waf @@ -1 +1 @@ -Subproject commit e7a75df6531beec1c1b0d18fcaf2cfce7693920c +Subproject commit ad08908c452c6a9bbb3bf7bbbcc9fc03fe46cc7f

RTEMS python standardisation

Hello, I know you must be consumed into other work and repositories, but I have been waiting for your response on the proposal and patch. I just need a starting point and Is there any guide for python repositories testing, I can see a lot of discussion in the past 2 days. I really look forward to

Re: Build FreeBSD: FAILED 5/rtems-mips on x86_64-freebsd12.1 (mipstx39-rtems5-gdb-8.0.1-x86_64-freebsd12.1-1)

On 18/3/20 5:29 pm, Sebastian Huber wrote: > On 18/03/2020 07:24, Chris Johns wrote: >> On 18/3/20 5:12 pm, Sebastian Huber wrote: >>> I don't have this fail on my FreeBSD 12.1 VM: >>> >>> https://lists.rtems.org/pipermail/build/2020-March/011712.html >>> >>> I use the GNU sed to build the tools.

Re: Build FreeBSD: FAILED 5/rtems-mips on x86_64-freebsd12.1 (mipstx39-rtems5-gdb-8.0.1-x86_64-freebsd12.1-1)

On 18/03/2020 07:24, Chris Johns wrote: On 18/3/20 5:12 pm, Sebastian Huber wrote: I don't have this fail on my FreeBSD 12.1 VM: https://lists.rtems.org/pipermail/build/2020-March/011712.html I use the GNU sed to build the tools. Hmmm, I am undecided if it is too late in the release cycle

Re: Build FreeBSD: FAILED 5/rtems-mips on x86_64-freebsd12.1 (mipstx39-rtems5-gdb-8.0.1-x86_64-freebsd12.1-1)

On 18/3/20 5:12 pm, Sebastian Huber wrote: > I don't have this fail on my FreeBSD 12.1 VM: > > https://lists.rtems.org/pipermail/build/2020-March/011712.html > > I use the GNU sed to build the tools. > Hmmm, I am undecided if it is too late in the release cycle to check for GNU sed and build

Re: Build FreeBSD: FAILED 5/rtems-mips on x86_64-freebsd12.1 (mipstx39-rtems5-gdb-8.0.1-x86_64-freebsd12.1-1)

I don't have this fail on my FreeBSD 12.1 VM: https://lists.rtems.org/pipermail/build/2020-March/011712.html I use the GNU sed to build the tools. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Build Linux: FAILED 6/rtems-riscv on x86_64-linux-gnu (riscv-rtems6-gdb-771dd3a-x86_64-linux-gnu-1)

On 18/03/2020 05:53, j...@rtems.org wrote: libtool: compile: gcc -O2 -g -pipe -I/home/joel/rtems-cron-6/rtems-source-builder/rtems/build/tmp/sb-1001/6/rtems-riscv/home/joel/rtems-cron-6/tools/6/include -DHAVE_CONFIG_H -I. -I../../sourceware-mirror-binutils-gdb-771dd3a/bfd

Re: [PATCH v2] eng: Add Python development guidelines

On 18/3/20 4:52 pm, Sebastian Huber wrote: > On 18/03/2020 06:28, Chris Johns wrote: > >> Build System >> >> >> Any need to have something about the build system to be used to wrap a >> project? >> There is waf as used in rtems-tools and then are are Python packaging >> systems. >>