On Mon, Jan 4, 2016 at 2:04 PM, Joel Sherrill wrote:
>
>
> On Mon, Jan 4, 2016 at 3:48 AM, Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
>
>>
>>
>> On 23/12/15 22:22, Marcos Díaz wrote:
>>
>>> That patch didn't work,
>>> one reason is that it has a mistake:
>>>
- Am 4. Jan 2016 um 18:01 schrieb Joel Sherrill j...@rtems.org:
> What exactly does this fix and how does it fix it?
I will add this to the commit message:
On certain targets (e.g. PowerPC) global data below a certain threshold (e.g. 8
bytes) may resided in a special memory area, the
Hi, i run some tests with do_one script on realview_pbx_a9_qemu
several months ago. I was wondering: how simple is to add a new bsp
for example i would like to run tests for Stellaris lm3s6965 (which is
supported by qemu).
-Is this just configuration and adding a simple exp file?
-I just need to
On Mon, Jan 4, 2016 at 12:58 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> - Am 4. Jan 2016 um 18:01 schrieb Joel Sherrill j...@rtems.org:
>
> > What exactly does this fix and how does it fix it?
>
> I will add this to the commit message:
>
> On certain targets (e.g.
On 28/12/15 19:14, Martin Galvan wrote:
Hi everyone! We're still looking into the issue Marcos described here:
https://lists.rtems.org/pipermail/devel/2015-December/013216.html
We noticed the problem seems to go away if we set the ticker interrupt
priority to be the same as for the other
On 23/12/15 22:22, Marcos Díaz wrote:
That patch didn't work,
one reason is that it has a mistake:
in kern_tc.c you defined this macro:
#define _Timecounter_Release(lock_context) \
+ *_ISR_lock_ISR_disable_and_acquire*(&_Timecounter_Lock, lock_context)
I think you meant:
On 27/12/15 23:43, Aun-Ali Zaidi wrote:
From: Tim Cussins
DHCP requests add the hostname option in dhcp_request_req() - this is cool,
except that the dhcp
spec requires that this option has a length >= 1 char.
Excerpt taken from RFC 2132:
3.14. Host Name Option
---
linkers/rtems-syms.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp
index c8f54ae..97315ac 100644
--- a/linkers/rtems-syms.cpp
+++ b/linkers/rtems-syms.cpp
@@ -104,7 +104,7 @@ static const char* c_trailer[] =
static const
---
linkers/rtems-syms.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp
index 97315ac..f0ffe94 100644
--- a/linkers/rtems-syms.cpp
+++ b/linkers/rtems-syms.cpp
@@ -60,7 +60,7 @@ static const char* c_header[] =
" */",
The rand() function doesn't produce a client specific random number.
Its not clear to me how the bug is actually addressed.
On 28/12/15 19:23, Aun-Ali Zaidi wrote:
From: Tim Cussins
The DHCP code in rtems uses an unchanging transaction id (xid) in the dhcp
discover and
Hello Owen,
this page contains out of date information. Use the RSB to create a tool
chain for MinGW and use msys2. I currently don't have time to document
the steps, but it works quite well with msys2.
On 30/12/15 01:27, Owen Pan wrote:
Hi all,
I am trying to bootstrap RTEMS on Windows
On 01/04/16 20:10, Sebastian Huber wrote:
this page contains out of date information.
I agree.
Use the RSB to create a tool
chain for MinGW and use msys2. I currently don't have time to document
the steps, but it works quite well with msys2.
There is an active GCI task about this which is
On 01/05/16 05:58, Sebastian Huber wrote:
- Am 4. Jan 2016 um 18:01 schrieb Joel Sherrill j...@rtems.org:
What exactly does this fix and how does it fix it?
I will add this to the commit message:
On certain targets (e.g. PowerPC) global data below a certain threshold (e.g. 8
bytes)
Hi
This is before and after for ticker.
text databssdechex filename
169644 2260 16605288 16777192 e8
ticker-executables-before/powerpc-psim-ticker.ralf
127352 2216 16647628 16777196 ec
ticker-executables/powerpc-psim-ticker.ralf
That is a pretty sizable drop (25%)
On 04/01/16 12:55, Daniel Gutson wrote:
>
>> +
>> + if ( (hostnamelen > 0) && (hostnamelen < 256) )
Avoid magic numbers. Should this be MAXHOSTNAMELEN, and in any case ot
has been already limited before in the call to gethosname turning the
check unnecessary? (Don't believe me, please
Hello Chris,
I used the versions of the contrib/download_prerequisites script of the GCC.
On 05/01/16 00:23, Chris Johns wrote:
Hi Sebastian,
Looking at 4.12 build in the RSB I see:
mpfr2.4.2
mpc0.8.1
gmp4.3.2
The 4.11 gcc-4.9.3 is using:
mpfr3.0.1
mpc
Hi
I think I cleaned everything up and did grep's after each architecture to
make sure it was gone except for standard GNU files.
That said, I could easily have made a mistake. If anyone spots anything
questionable, please speak up.
FWIW there are other repos which need to be swept. These
Hi Sebastian,
Looking at 4.12 build in the RSB I see:
mpfr 2.4.2
mpc0.8.1
gmp4.3.2
The 4.11 gcc-4.9.3 is using:
mpfr 3.0.1
mpc0.8.2
gmp5.0.5
4.12/rtems-arm builds on FreeBSD.
Ok to update to the 4.11 versions?
Chris
On Mon, Jan 4, 2016 at 3:48 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 23/12/15 22:22, Marcos Díaz wrote:
>
>> That patch didn't work,
>> one reason is that it has a mistake:
>> in kern_tc.c you defined this macro:
>>
>> #define _Timecounter_Release(lock_context) \
On Sun, Jan 3, 2016 at 11:00 PM, Gedare Bloom wrote:
> On Sun, Jan 3, 2016 at 9:47 PM, Joel Sherrill wrote:
> >
> >
> > On Sun, Jan 3, 2016 at 8:26 PM, Chris Johns wrote:
> >> Can you get a suitable list of functions that must be present in
20 matches
Mail list logo