Re: Can't enable a dummy clock driver

2017-07-23 Thread Denis Obrezkov
2017-07-24 8:27 GMT+02:00 Hesham Almatary : > On Mon, Jul 24, 2017 at 8:27 AM, Joel Sherrill wrote: > > > > > > On Jul 23, 2017 5:15 PM, "Denis Obrezkov" > wrote: > > > > 2017-07-23 22:30 GMT+02:00 Joel Sherrill : > >> > >> Increasing the stack size effectively eliminated a data corruption > iss

rtems microblaze rsb build failure in 4.12

2017-07-23 Thread yao0718
I try to build tools of microblaze by rsb, but I get failure when build newlib libm, the log is: /opt/rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.3.0-newlib-2.5.0.20170323-i686-linux-gnu-1/build/./gcc/xgcc -B/opt/rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.3.0-new

Re: [PATCH-v2] sparc: Rename NGMP to GR740 and add configs for UT699, UT700, and GR712RC

2017-07-23 Thread Sebastian Huber
On 19/07/17 22:35, Jiri Gaisler wrote: The instruction that takes the trap is at 0x40004040, which is ld [ %sp + 0x4c ], %f8. Remember that SPARC has deferred FPU trap model so it is actually the previous FPU instruction FSMULD at 0x4000403c that generated the trap. This instruction is not impl

Re: [PATCH] [SPARC] Disable muldf3_extend for LEON targets

2017-07-23 Thread Sebastian Huber
On 20/07/17 10:38, Sebastian Huber wrote: Since a prominent LEON2 chip, the AT697F, does not support the FSMULD instruction, disable it for all LEON2 targets due to simplicity. The code generation for the fmaf() function of Newlib changes for example from Tests on a real AT697F showed that it

Re: Can't enable a dummy clock driver

2017-07-23 Thread Hesham Almatary
On Mon, Jul 24, 2017 at 8:27 AM, Joel Sherrill wrote: > > > On Jul 23, 2017 5:15 PM, "Denis Obrezkov" wrote: > > 2017-07-23 22:30 GMT+02:00 Joel Sherrill : >> >> Increasing the stack size effectively eliminated a data corruption issue. >> The memory corrupted likely was an RTEMS internal object s

Re: Can't enable a dummy clock driver

2017-07-23 Thread Joel Sherrill
On Jul 23, 2017 5:15 PM, "Denis Obrezkov" wrote: 2017-07-23 22:30 GMT+02:00 Joel Sherrill : > Increasing the stack size effectively eliminated a data corruption issue. > The memory corrupted likely was an RTEMS internal object structure. > > What is the stack frame size required by each subrouti

Re: Can't enable a dummy clock driver

2017-07-23 Thread Denis Obrezkov
2017-07-23 22:30 GMT+02:00 Joel Sherrill : > Increasing the stack size effectively eliminated a data corruption issue. > The memory corrupted likely was an RTEMS internal object structure. > > What is the stack frame size required by each subroutine call? > How can I determine it? > > How much st

Re: Can't enable a dummy clock driver

2017-07-23 Thread Denis Obrezkov
2017-07-23 15:20 GMT+02:00 Denis Obrezkov : > 2017-07-22 21:24 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 22, 2017 3:01 PM, "Denis Obrezkov" >> wrote: >> >> Hello, I am trying to enable a dummy clock driver. >> I did as Joel suggested like in v850sim BSP. >> But now I have a problem - the driver

Re: libbsd include path issue

2017-07-23 Thread Christian Mauderer
Am 23.07.2017 um 15:57 schrieb Gedare Bloom: > On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer > wrote: >> Am 23.07.2017 um 14:05 schrieb Gedare Bloom: >>> On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote: On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote: > On Sat, Jul 22,

Re: libbsd include path issue

2017-07-23 Thread Gedare Bloom
On Sun, Jul 23, 2017 at 8:38 AM, Christian Mauderer wrote: > Am 23.07.2017 um 14:05 schrieb Gedare Bloom: >> On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote: >>> On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote: On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer wrote: >

Re: Can't enable a dummy clock driver

2017-07-23 Thread Denis Obrezkov
2017-07-22 21:24 GMT+02:00 Joel Sherrill : > > > On Jul 22, 2017 3:01 PM, "Denis Obrezkov" wrote: > > Hello, I am trying to enable a dummy clock driver. > I did as Joel suggested like in v850sim BSP. > But now I have a problem - the driver isn't initialized properly. > I receive an exception "Ill

Re: libbsd include path issue

2017-07-23 Thread Christian Mauderer
Am 23.07.2017 um 14:05 schrieb Gedare Bloom: > On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote: >> On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote: >>> On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer >>> wrote: Hello Sichen, as discussed in our private chat I'm quite

Re: libbsd include path issue

2017-07-23 Thread Gedare Bloom
On Sun, Jul 23, 2017 at 8:04 AM, Gedare Bloom wrote: > On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote: >> On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer >> wrote: >>> Hello Sichen, >>> >>> as discussed in our private chat I'm quite convinced that your problem >>> is that the source fi

Re: libbsd include path issue

2017-07-23 Thread Gedare Bloom
On Sun, Jul 23, 2017 at 7:49 AM, Gedare Bloom wrote: > On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer > wrote: >> Hello Sichen, >> >> as discussed in our private chat I'm quite convinced that your problem >> is that the source file is in "freebsd/crypto/openssl/crypto" which >> doesn't end

Re: libbsd include path issue

2017-07-23 Thread Gedare Bloom
On Sat, Jul 22, 2017 at 1:30 PM, Christian Mauderer wrote: > Hello Sichen, > > as discussed in our private chat I'm quite convinced that your problem > is that the source file is in "freebsd/crypto/openssl/crypto" which > doesn't end on a path called "openssl". > > As far as I can see, there is cu

Re: [PATCH] waf_generator: Copy headers if necessary.

2017-07-23 Thread Sichen Zhao
Hi all, I have tested the patch in libbsd, and it works well. Best Regards Sichen Zhao From: Christian Mauderer Sent: Sunday, July 23, 2017 1:30 To: devel@rtems.org Cc: Chris Johns; Sichen Zhao; Christian Mauderer Subject: [PATCH] waf_generator: Copy head