On 5/11/2014 6:14 pm, Sebastian Huber wrote:
on the latest Git master the following new tests fail on
arm/realview_pbx_a9_qemu due to a timeout after 180 seconds: top,
dl01.pre and dl02.pre.
The dl01.pre and dl02.pre are not to be run. They are the first link of
two to get a suitable set of
I'm in support of putting bsp-specific examples in examples-v2. And
renaming the repository...
Reducing repo sprawl is good.
-Gedare
On Wed, Nov 5, 2014 at 12:32 AM, Chris Johns wrote:
> On 5/11/2014 2:40 pm, Gedare Bloom wrote:
>>
>> These are ideal for BSP-specific testing framework, which we
I'm not sure any of the ARM BSPs use the abort.c or simple_abort.c, even if
they have the code included.
I don't have access to the code right now, but I will take a look at the
ARM BSPs and remove it from the ones that use the shared start.S.
If the ARM BSPs that do not use the shared start.S inc
On 05/11/14 15:35, Alan Cudmore wrote:
If the ARM BSPs that do not use the shared start.S include the code, but never
call it, I can remove it, if that is what is best. We could even remove abort.c
and simple_abort.c completely. Just let me know.
It would be best to get rid of these files.
--
This is a tough problem. We have plenty of inexpensive SPI and I2C devices
to mix and match with low cost boards such as the Pi and Beaglebone, but it
could all become obsolete quickly.
If we put a bunch of SPI and I2C drivers in the RTEMS repo, then how do we
test and maintain them without duplica
How are interactive tests being handled now? The top test will
eventually end but would come closest to being considered
interactive.
Jennifer Averett
> -Original Message-
> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Sebastian
> Huber
> Sent: Wednesday, November 05, 2014
A standalone framework for drivers would be quite useful. That, or
improved support for drivers (HAL) in RTEMS is needed to achieve a
maintainable solution. -Gedare
On Wed, Nov 5, 2014 at 10:10 AM, Alan Cudmore wrote:
> This is a tough problem. We have plenty of inexpensive SPI and I2C devices
>
---
cpukit/libmisc/shell/main_edit.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/cpukit/libmisc/shell/main_edit.c b/cpukit/libmisc/shell/main_edit.c
index fc7775c..0feb828 100644
--- a/cpukit/libmisc/shell/main_edit.c
+++ b/cpukit/libmisc/shell/main_edit
---
.../lpc176x/make/custom/lpc1768_mbed_ahb_ram_eth-testsuite.tcfg | 8
1 file changed, 8 insertions(+)
diff --git
a/c/src/lib/libbsp/arm/lpc176x/make/custom/lpc1768_mbed_ahb_ram_eth-testsuite.tcfg
b/c/src/lib/libbsp/arm/lpc176x/make/custom/lpc1768_mbed_ahb_ram_eth-testsuite.tcfg
i
---
c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc23xx_tli800-testsuite.tcfg | 1 +
1 file changed, 1 insertion(+)
diff --git
a/c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc23xx_tli800-testsuite.tcfg
b/c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc23xx_tli800-testsuite.tcfg
index 5d303a9..9c10352 10
---
c/src/lib/libbsp/arm/lm3s69xx/make/custom/lm3s3749-testsuite.tcfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/c/src/lib/libbsp/arm/lm3s69xx/make/custom/lm3s3749-testsuite.tcfg
b/c/src/lib/libbsp/arm/lm3s69xx/make/custom/lm3s3749-testsuite.tcfg
index 30aaea0..9462da2 100644
--- a/c/src
---
c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc2362-testsuite.tcfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc2362-testsuite.tcfg
b/c/src/lib/libbsp/arm/lpc24xx/make/custom/lpc2362-testsuite.tcfg
index 1559e3d..d1b31fa 100644
--- a/c/src/lib/l
Hi
I just thought I would post a summary after the recent updates
and include all targets in one easy to track email. Overall about
50% of the architectures fail to build for some reason or another.
+ Unrecognized symbol type from a .s file
bfin (all BSPs), i386 (all BSPs), powerpc (all BSPs)
Which targets do you think this fixes?
On November 5, 2014 7:02:32 PM CST, Chris Johns wrote:
>Module:rtems-tools
>Branch:master
>Commit:b9c0a0436d387429035241d3d4d03446b6f915cf
>Changeset:
>http://git.rtems.org/rtems-tools/commit/?id=b9c0a0436d387429035241d3d4d03446b6f915cf
>
>Author
On 6/11/2014 11:08 am, Joel Sherrill wrote:
I just thought I would post a summary after the recent updates
and include all targets in one easy to track email. Overall about
50% of the architectures fail to build for some reason or another.
+ Unrecognized symbol type from a .s file
bfin (all B
On 6/11/2014 12:15 pm, Joel Sherrill wrote:
Which targets do you think this fixes?
The i386 now builds. See my other email.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hello Jennifer,
yes, there are some interactive tests in the test suite, but do we really need
new ones? Who has the time to do interactive testing?
The other interactive tests wait some seconds for user input and otherwise
exit. I think it is preferable to turn this top test into a non-int
Hello,
I have a new item for the list:
Very desirable
==
+ Since red-black trees are now used to implement the priority queues and they
will play an important part in future SMP improvements I would like to do some
performance measurements with alternative implementations. I woul
18 matches
Mail list logo
