Re: [rtems commit] Fix or1k C++ build failure

I doubt that this fix is correct. This variable is usually defined in the GCC libgcc/crtstuff.c file. I guess something is wrong with the GCC configuration for this target. On 26/04/15 21:56, Joel Sherril wrote: Module:rtems Branch:master Commit:3dead51eddcdb734b36c949cbc1e4c2cd21c

Re: 4.11 Branching

On April 26, 2015 8:41:34 PM CDT, Chris Johns wrote: >On 27/04/2015 11:15 am, Joel Sherrill wrote: >> >> Anything else? > >I have a change for the cpuuse top command to correctly display the >current usage rather than the total usage. This is not a bug fix as >such >so I am not sure it is ok t

Re: 4.11 Branching

On 27/04/2015 11:15 am, Joel Sherrill wrote: > > Anything else? I have a change for the cpuuse top command to correctly display the current usage rather than the total usage. This is not a bug fix as such so I am not sure it is ok to go in. Chris ___

4.11 Branching

Hi I have a fix in the test queue for the build breakages I reported last week. Hesham fixed C++ on the or1k. I need to bump the dates on the documentation before branching. I had the impression Sebastian wanted to merge one more patch set. Is this true? Anything else? --joel ___

[PATCH] Fix or1k C++ build failure

Closes #2329 --- c/src/lib/libbsp/or1k/generic_or1k/start/start.S | 7 +++ 1 file changed, 7 insertions(+) diff --git a/c/src/lib/libbsp/or1k/generic_or1k/start/start.S b/c/src/lib/libbsp/or1k/generic_or1k/start/start.S index d951a55..ae6d41a 100644 --- a/c/src/lib/libbsp/or1k/generic_or1k/s

Re: [PATCH] Beagle BSP Improvements (GPIO driver)

All, I think the API as it is (for digital GPIO's) is pretty close to generic. I like my suggestion (gpio_* in my previous mail) better as more generic. (More configuration is hidden from the application.) Joel I just read your presentation. I have come up with a minimal GPIO API based on the ab