> On 26 Nov 2018, at 5:21 pm, Vijay Kumar Banerjee
> wrote:
> I'm getting the result Invalid while running hello.exe with rtems-test on
> leon3 (without coverage option)
> attaching the log.
Can you please revert or not apply patch 1 and let me know what happens? I have
a feeling the
I'm getting the result Invalid while running hello.exe with rtems-test on
leon3 (without coverage option)
attaching the log.
On Mon, 26 Nov 2018 at 06:40, wrote:
> Hi,
>
> Please test these patches and report.
>
> The patches:
>
> - Add unittests for the rtemstoolkit python modules. To run
Hi,
Does this test require user input or is it suppose to pass?
If it does require user input should it be tagged as USER_INPUT?
I am seeing a time out on sparc/erc32.
Chris
___
devel mailing list
devel@rtems.org
From: Chris Johns
- Add support to run the unit tests for the rtemstoolkit python
modules from waf. Enter './waf test' for the tests to be run on
python2 and python3.
- Update the importing of rtemstoolkit modules to the standard
method which works on python2 and python3.
- Update the
From: Chris Johns
- Use the 'read1' file handle call to return if any data is queued
for reading from stdout or stderr.
- Flush the stdin pipe in the writer thread.
These changes let the execute module work on Python2 and Python3.
---
rtemstoolkit/execute.py | 3 ++-
1 file changed, 2
From: Chris Johns
The command line changed and the RSB is the newer version. Make
the old version via a config variable.
---
tester/rtems/testing/qemu.cfg | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tester/rtems/testing/qemu.cfg b/tester/rtems/testing/qemu.cfg
From: Chris Johns
---
rtemstoolkit/git.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/rtemstoolkit/git.py b/rtemstoolkit/git.py
index e1dd029..b92391f 100644
--- a/rtemstoolkit/git.py
+++ b/rtemstoolkit/git.py
@@ -152,7 +152,10 @@ class repo:
def dirty(self):
From: Chris Johns
- Use buffered output on the stdout and stderr streams from
child processors.
- Simplify the read thread line processing to improve performance.
- Disable 'close_fds' as it slows down python3's popen call.
- Update the importing of rtemstoolkit modules.
---
From: Chris Johns
- Fix mi_parser on Python3. Python3 does not support the __cmp__
operator and rich comparision operators are required, See PEP 207.
- Remove the global variables and make a class containing them. Update
the gdb class to use the mi_parser session class. Removing the globals
Hi,
Please test these patches and report.
The patches:
- Add unittests for the rtemstoolkit python modules. To run enter:
./waf test
The tests will be run for python2 and python3 is present on your
host.
- Improvie the reader thread line processor of child process stdio
data. Switch
Hello,
I just enabled the per-function and per-data element section support for
the uC5282 bsp in m68k architecture .
The patch for the change has been attached
Thank you
Regards
--Shashvat
0001-m68k-uC5282-Add-per-section-compilation-and-linking-.patch
Description: Binary data
Hello Peter,
Thomas mentioned already the bug that has been reported to Microchip.
Please note that I had two more problems with the BSP on another
customers board:
- The core clock couldn't be set to the maximum frequency from the data
sheet. Both possible configurations for that frequency
Thank you for the advice. I will not need USB, but will need SDRAM and don’t
need poor support. Microchip? You tried to push RTEMS for this platform tied
to space applications, are you monitoring this? The platform looks like just
what I need but not if you’re not supporting it.
> On Nov
Peter,
just to make you aware: we designed a board with the ATSAMV7 chip and hit some
nasty and at least one really ugly bug: operating the USB interface
concurrently with external SDRAM does not work. Half a year after reporting
this bug, Microchip confirmed it, but did not plan any fix for
I need to evaluate this for a multi-chip application.
This part is a result of Microchip’s take-over of ATMEL. I’m double-checking
that to create a BSP based on this I should start with the existing ATSAMV7
BSP, I think the peripherals (e.g. network chip and so on) are the same as the
Odd comments:
+ Use the -vN option to git format-patch and don't manually put the
version number in the commit message
+ Put a space before the first parenthesis on the log message.
I have fixed this a couple of times for you and figure you will do more
tasks so
might as well have it right when
Should be OK now. Double check the ticket closed. :)
Thanks.
--joel
On Sun, Nov 25, 2018 at 1:58 AM Shashvat Jain
wrote:
> I managed to do " git --amend " here is the updated patch with message
> "Closes #2566"
>
> thank you
> Regards
>
> --Shashvat
>
> On Sun, Nov 25, 2018 at 1:23 PM
Hi guys,
Here is the patch file with output
https://paste.ofcode.org/khkkS9SLwsTtDUCPHAipCa .
Thanks
himanshu
From d7f591df5f723d11f56495764c52b0f60427c7b1 Mon Sep 17 00:00:00 2001
From: Himanshu40
Date: Sun, 25 Nov 2018 15:12:52 +0530
Subject: [PATCH] psxtmtests: add psxtmmqrcvblock02 -v2(GCI
---
tester/covoar/wscript | 1 +
tester/rt/coverage.py | 13 -
tester/rt/test.py | 2 ++
3 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/tester/covoar/wscript b/tester/covoar/wscript
index d447117..a3730ea 100644
--- a/tester/covoar/wscript
+++
On Sun, 25 Nov 2018 at 02:42, Chris Johns wrote:
> On 24/11/18 6:55 pm, Vijay Kumar Banerjee wrote:
> >
> > OK, we just need a patch. :)
> >
> > this worked
> >
> > diff --git a/tester/covoar/wscript b/tester/covoar/wscript
> > index d447117..bf70bfb 100644
> > ---
20 matches
Mail list logo
