Re: [PATCH 3/5] libstdthreads/thrd.c: Mark path as unreachable on GCC to resolve warning

On 21/03/16 17:53, Joel Sherrill wrote: On Mon, Mar 21, 2016 at 7:33 AM, Sebastian Huber > wrote: On 21/03/16 13:31, Joel Sherrill wrote: On Mon, Mar 21, 2016 at 1:26 AM, Sebastian Huber mailto:sebastian.hu...@embedded-bra

[PATCH 1/2] score: Add RTEMS_UNREACHABLE

--- cpukit/score/include/rtems/score/basedefs.h | 9 + 1 file changed, 9 insertions(+) diff --git a/cpukit/score/include/rtems/score/basedefs.h b/cpukit/score/include/rtems/score/basedefs.h index facaed9..5d7f5b4 100644 --- a/cpukit/score/include/rtems/score/basedefs.h +++ b/cpukit/score

[PATCH 2/2] posix: pthread_exit() is a no-return function

--- cpukit/posix/src/pthreadexit.c | 1 + 1 file changed, 1 insertion(+) diff --git a/cpukit/posix/src/pthreadexit.c b/cpukit/posix/src/pthreadexit.c index 6b3a09a..6f8a7a7 100644 --- a/cpukit/posix/src/pthreadexit.c +++ b/cpukit/posix/src/pthreadexit.c @@ -75,4 +75,5 @@ void pthread_exit( ) {

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

Thanks Gedare. Both work fine with or1ksim and qemu. On Tue, Mar 22, 2016 at 11:30 AM, Gedare Bloom wrote: > Hi Hesham, > > I think the 4.12 patch is there. (updates 2669) > > On Mon, Mar 21, 2016 at 6:49 PM, Hesham Almatary > wrote: >> The patch works fine for 4.11 branches on both or1ksim and

Re: [PATCH] rtems: Rework rate-monotonic scheduler

Looks good. On Mon, Mar 21, 2016 at 10:40 AM, Sebastian Huber wrote: > Use the default thread lock to protect rate-monotonic state changes. > his avoids use of the Giant lock. Split rtems_rate_monotonic_period() > body into several static functions. Introduce a new thread wait class > THREAD_WA

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

Hi Hesham, I think the 4.12 patch is there. (updates 2669) On Mon, Mar 21, 2016 at 6:49 PM, Hesham Almatary wrote: > The patch works fine for 4.11 branches on both or1ksim and qemu. 4.12 > patch will be really appreciated. > > On Mon, Mar 21, 2016 at 8:34 AM, Hesham Almatary > wrote: >> On Mon,

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

The patch works fine for 4.11 branches on both or1ksim and qemu. 4.12 patch will be really appreciated. On Mon, Mar 21, 2016 at 8:34 AM, Hesham Almatary wrote: > On Mon, Mar 21, 2016 at 8:24 AM, Stefan Wallentowitz > wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 20.03.2016

Re: [PATCH 3/5] libstdthreads/thrd.c: Mark path as unreachable on GCC to resolve warning

On Mon, Mar 21, 2016 at 7:33 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 21/03/16 13:31, Joel Sherrill wrote: > >> >> >> On Mon, Mar 21, 2016 at 1:26 AM, Sebastian Huber < >> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote: >> >> >> >>

Re: GSoC 2016 Participation

Thanks for the prompt reply. Is there any other open project related to resource management or scheduling in which I can contribute? On Mon, Mar 21, 2016 at 8:00 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > They are already implemented, but since there is currently no use ca

[PATCH] rtems: Rework rate-monotonic scheduler

Use the default thread lock to protect rate-monotonic state changes. his avoids use of the Giant lock. Split rtems_rate_monotonic_period() body into several static functions. Introduce a new thread wait class THREAD_WAIT_CLASS_PERIOD for period objects to synchronize the blocking operation. Clos

Re: GSoC 2016 Participation

Will implementation of phase fair RW locks be considered in this GSOC? I know I am very late to ask this question. I have read the concept and theory of phase fair RW locks from reference suggested in RTEMS( http://www.mpi-sws.org/~bbb/papers/pdf/rtsj11.pdf) On Mon, Mar 21, 2016 at 12:02 PM, Sebas

Re: GSoC 2016 Participation

They are already implemented, but since there is currently no use case for them, they are not included in the sources. On 21/03/16 15:29, Rahul Goradia wrote: Will implementation of phase fair RW locks be considered in this GSOC? I know I am very late to ask this question. I have read the conce

Re: Request for GPIO Examples

On 16 Mar 2016 at 2:30, punit vara wrote: > > Hi > > > > Are there any example programs for the GPIO? I realize they would be > > specific to the BBB or Pi but would appreciate getting some code. > > > > Thanks. > > > > --joel > I tested GPIO APIs in Beaglebone black with LED blinking. You can loo

Re: [PATCH 3/5] libstdthreads/thrd.c: Mark path as unreachable on GCC to resolve warning

On 21/03/16 13:31, Joel Sherrill wrote: On Mon, Mar 21, 2016 at 1:26 AM, Sebastian Huber > wrote: On 20/03/16 21:40, Joel Sherrill wrote: --- cpukit/libstdthreads/thrd.c | 3 +++ 1 file changed, 3 insertions(+)

Re: [PATCH 3/5] libstdthreads/thrd.c: Mark path as unreachable on GCC to resolve warning

On Mon, Mar 21, 2016 at 1:26 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 20/03/16 21:40, Joel Sherrill wrote: > >> --- >> cpukit/libstdthreads/thrd.c | 3 +++ >> 1 file changed, 3 insertions(+) >> >> diff --git a/cpukit/libstdthreads/thrd.c b/cpukit/libstdthreads/t