Re: [PATCH 1/4] cpukit: Add and use Watchdog_Discipline.

Hello Gedare, I am happy in general, but I have some concerns. I would definitely not change the Classic API level ticks based interfaces from 32-bit intervals to 64-bit intervals. There is no benefit from having 64-bits at this level. On 23/06/16 21:26, Gedare Bloom wrote: Clock discipline

[PATCH 4/4] score: use 64-bit watchdog intervals

updates #2732 --- cpukit/score/include/rtems/score/watchdog.h | 2 +- testsuites/sptests/sp37/init.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/cpukit/score/include/rtems/score/watchdog.h b/cpukit/score/include/rtems/score/watchdog.h index 11a5974..1f4c3e1

[PATCH 2/4] posix: add clock_nanosleep and tests

updates #2732 --- cpukit/posix/src/nanosleep.c | 55 -- testsuites/psxtests/psxhdrs/Makefile.am| 1 + testsuites/psxtests/psxhdrs/time/clock_nanosleep.c | 35 +++ testsuites/psxtmtests/Makefile.am | 3 + testsuites/psxtmtests/con

[PATCH 1/4] cpukit: Add and use Watchdog_Discipline.

Clock disciplines may be WATCHDOG_RELATIVE, WATCHDOG_ABSOLUTE, or WATCHDOG_NO_TIMEOUT. A discipline of WATCHDOG_RELATIVE with a timeout of WATCHDOG_NO_TIMEOUT is equivalent to a discipline of WATCHDOG_NO_TIMEOUT. updates #2732 --- cpukit/libnetworking/rtems/rtems_glue.c| 5 ++- cpuki

[PATCH 3/4] cpukit/rtems: fix return type mismatch for _TOD_To_seconds

--- cpukit/rtems/src/clocktodtoseconds.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/rtems/src/clocktodtoseconds.c b/cpukit/rtems/src/clocktodtoseconds.c index bab9f85..99d0cbd 100644 --- a/cpukit/rtems/src/clocktodtoseconds.c +++ b/cpukit/rtems/src/clocktodtosecond

[PATCH 2/2] posix: cond_timedwait remember and use clock from condattr

updates #2745 --- cpukit/posix/include/rtems/posix/cond.h | 1 + cpukit/posix/include/rtems/posix/condimpl.h | 4 +++- cpukit/posix/src/condinit.c | 2 +- cpukit/posix/src/condtimedwait.c| 3 +++ cpukit/posix/src/condwaitsupp.c | 3 ++- cpukit/posix/src/

[PATCH 1/2] posix: refactor cond wait support to defer abstime conversion

updates #2745 --- cpukit/posix/include/rtems/posix/condimpl.h | 3 +-- cpukit/posix/src/condtimedwait.c| 25 + cpukit/posix/src/condwait.c | 3 +-- cpukit/posix/src/condwaitsupp.c | 29 +++-- 4 files changed,

Beagle bone black BSP broken

Recently I updated rtems from mainline repo. and tried to build BBB BSP but got following errors. It seems BSP is broken. Up to 17th June I was successfully able to compile BSP. ../../../../../../../../../../rtems-src/c/src/lib/libbsp/arm/beagle/console/console-config.c:151:1: error: unknown type

[PATCH 0/4] Progress toward absolute time intervals

These patches move forward toward a goal to provide support for the CLOCK_ABSTIME in POSIX. The first service targeted is the clock_nanosleep, with others to follow. The bulk of changes here are to add separate watchdog disciplines for relative and absolute time intervals. This adds timeout fields

PCIe on QorIQ?

Hi Has anyone used PCIe on a QorIQ reference board or any other QorIQ board? What functionality is missing in the empty p ci express structures in the BSP? Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/d

Re: [PATCH] Subject: Add PWM driver for beagle bone black

Hi Punit, Great to see PWM driver working Besides Martin has suggested, I would like to add few points. On 21 June 2016 at 21:56, Punit Vara wrote: > This patch adds required definitions, registers definitions and > testsuit to > test pwm driver for beagle bone black. > ---

Re: tester failures

Nevermind! The problems appear to be in my changes. Guess I found my own bugs to fix. On Thu, Jun 23, 2016 at 11:24 AM, Gedare Bloom wrote: > I also had 10 new timeouts. I'll build a clean head and compare results.. > > On Thu, Jun 23, 2016 at 11:23 AM, Gedare Bloom wrote: >> I ran tester for si

Re: Mailbox RPi patch and rtems_cache_* probably broken on RPi

This could explain a number of problems reported by students trying to get their RPi peripherals working. The cache manager has never been a robust and complete implementation. I think it must be carefully looked at across targets (easier when we delete obsolete architectures!). It looks like ever

Re: tester failures

I also had 10 new timeouts. I'll build a clean head and compare results.. On Thu, Jun 23, 2016 at 11:23 AM, Gedare Bloom wrote: > I ran tester for sis last night after a rebase and see 4 new failures. > I have some local changes, but I suspect the failures affect the > vanilla HEAD too. log snipp

tester failures

I ran tester for sis last night after a rebase and see 4 new failures. I have some local changes, but I suspect the failures affect the vanilla HEAD too. log snippets below: > run: /home/gedare/install/bin/sparc-rtems4.12-run -a -nouartrx > ../../builds/b-sis/sparc-rtems4.12/c/sis/testsuites/libt

Re: Errors while building rtems-libbsd

Should now work again. -- 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.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschä

Errors while building rtems-libbsd

Hello, I am not able to build the current rtems-libbsd with all rtems and the tools updated for RPi. I tried to go back to previous commits, re-installed everything from the git.rtems.org, nothing worked. I am getting the following error. In file included from /home/gadgetman/development/rtems-li