On 22/11/14 04:36, Joel Sherrill wrote:
On November 21, 2014 5:50:08 PM CST, Chris Johns wrote:
>On 22/11/2014 1:53 am, Joel Sherrill wrote:
>>
>>On 11/21/2014 1:38 AM, Sebastian Huber wrote:
>>>On 20/11/14 22:08, Joel Sherrill wrote:
Hi
We have different code to process these
On Sun, Nov 23, 2014 at 6:10 PM, Amar Takhar wrote:
> On 2014-11-23 14:30 -0500, Gedare Bloom wrote:
>> > Components themselves should be very general. 'RTEMS', 'Build', 'Testing',
>> > 'BSP', 'CPU' etc.
>> >
With the 'arch' field, and ability to tag (e.g. on a bsp name), I
think we only need "RT
On 2014-11-23 14:30 -0500, Gedare Bloom wrote:
> > Components themselves should be very general. 'RTEMS', 'Build', 'Testing',
> > 'BSP', 'CPU' etc.
> >
> OK, if we define some tags and scope them right, this can work. I
> don't like the idea of a free-text field though. Can tags be a
> drop-down l
Hi
I am prone to say we treat tickets for "BSP Y is missing..."
and "add X to BSP Y" with extreme prejudice. Unless the
ticket is to track work that is submitted, someone is
actively working on, or something we want to have as
an Open Project, it is just going to be a zombie.
If we used tickets f
Condition needs to be inverted, as a 1 in the mask register means
that the interrupt is enabled. Solves ticket #1958 in trac.
---
c/src/lib/libbsp/sparc/leon3/include/leon.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/c/src/lib/libbsp/sparc/leon3/include/leon.h
b/c/src/
Condition needs to be inverted, as a 1 in the mask register means
that the interrupt is enabled. Solves ticket #1959 in trac.
---
c/src/lib/libbsp/sparc/leon2/include/leon.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/c/src/lib/libbsp/sparc/leon2/include/leon.h
b/c
On Sun, Nov 23, 2014 at 11:10 AM, Amar Takhar wrote:
> On 2014-11-23 10:28 -0500, Gedare Bloom wrote:
>
>> RTEMS (rtems.git) components:
>> * One component for each architecture family; for problems that affect
>> those archs or their bsps
>
> We have a 'tag cloud' that can be viewed here: https:
Thanks Jiri!
On Sun, Nov 23, 2014 at 1:22 PM, Jiri Gaisler wrote:
>
>
> On 11/23/2014 04:36 PM, Gedare Bloom wrote:
>> Is this fixed?
>
> Seems OK with the new version of sis. Below is the log from cdtest.exe.
> I'm using the leon3 bsp, but is should be the same on all sparc bsp's.
>
> Jiri.
>
>
On 11/23/2014 04:36 PM, Gedare Bloom wrote:
> Is this fixed?
Seems OK with the new version of sis. Below is the log from cdtest.exe.
I'm using the leon3 bsp, but is should be the same on all sparc bsp's.
Jiri.
$ sparc-rtems4.11-sis -leon3
src/rtems/4.11/sparc-rtems4.11/leon3/lib/rtems-4.11/t
On 2014-11-23 10:28 -0500, Gedare Bloom wrote:
> RTEMS (rtems.git) components:
> * One component for each architecture family; for problems that affect
> those archs or their bsps
We have a 'tag cloud' that can be viewed here: https://devel.rtems.org/tags
both tickets and wiki pages can be mark
Is this fixed?
> On Sun, Nov 23, 2014 at 10:13 AM, RTEMS trac wrote:
>> #2175: C++ Exception Catch Handler Crash on Sparc ERC32 Simulator(SIS)
>> --+-
>> Reporter: jbkim | Owner: ralf.corsepius
>> Type: defect| Status:
Hi,
TL;DR: Trac tickets are in a good state. We need to close or bump the
4.11 milestones before release. I'd like to discuss a proposal to
organize the Trac Tickets better.
One of the appeals of Trac is that it is simple.There are a six ways
I'd like to see our use of trac ticket management beco
12 matches
Mail list logo
