On 29/02/2016 01:48, Gedare Bloom wrote:
I'm in favor, because I have observed new users building the 4.11
tools and not knowing they have to branch to 4.11 in rtems.git. Having
to "branch" to get the 4.11 tools should help make the look-and-feel
be consistent.
Thanks for the feedback (and Joe
Btw, should this fix go to 4.11 as well?
On Sun, Feb 28, 2016 at 5:28 PM, Martin Galvan
wrote:
> Thanks a lot!
>
> On Sat, Feb 27, 2016 at 8:28 PM, Ben Gras wrote:
>> All,
>>
>> I tested this on current HEAD and verified it fixes a case I'd ran
>> into trouble with before, namely gpio-triggered
Thanks a lot!
On Sat, Feb 27, 2016 at 8:28 PM, Ben Gras wrote:
> All,
>
> I tested this on current HEAD and verified it fixes a case I'd ran
> into trouble with before, namely gpio-triggered irqs. Great to see. I
> pushed your change with a commit message based on your original email,
> Martin. I
I'm in favor, because I have observed new users building the 4.11
tools and not knowing they have to branch to 4.11 in rtems.git. Having
to "branch" to get the 4.11 tools should help make the look-and-feel
be consistent.
On Sat, Feb 27, 2016 at 8:06 PM, Joel Sherrill wrote:
>
> On Feb 27, 2016 5
Hi Animesh,
The RTEMS master branch assumes you are using the 4.12 RSB release (so
you have to replace your 4.11 built tools with a 4.12 build).
Regards,
Hesham
On Sun, Feb 28, 2016 at 4:46 AM, animesh pathak wrote:
> Hi, I am new to RTEMS. I am trying to setup the environment but getting
> err
