Re: [PATCH] bsps: Improve interrupt vector enable/disable API

On 20/06/17 02:51, Chris Johns wrote: On 19/06/2017 23:19, Sebastian Huber wrote: Change bsp_interrupt_vector_enable() and bsp_interrupt_vector_disable() to not return a status code. Add bsp_interrupt_assert() and use it to validate the vector number in the vector enable/disable

Re: RISC-V/HiFive memory limitations

On Jun 19, 2017 5:37 PM, "Denis Obrezkov" wrote: 2017-06-20 1:23 GMT+03:00 Hesham Almatary : > > > On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov > wrote: > >> 2017-06-20 0:19 GMT+03:00 Joel Sherrill :

Re: [PATCH] bsps: Improve interrupt vector enable/disable API

On Mon, Jun 19, 2017 at 2:45 PM, Christian Mauderer wrote: > - Ursprüngliche Mail - >> Von: "Gedare Bloom" >> An: "Sebastian Huber" >> CC: "RTEMS Devel" >> Gesendet:

Re: RISC-V/HiFive memory limitations

2017-06-20 1:23 GMT+03:00 Hesham Almatary : > > > On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov > wrote: > >> 2017-06-20 0:19 GMT+03:00 Joel Sherrill : >> >>> Check the value in gdb without loading it on a target. >>> >>> Gdb

Re: RISC-V/HiFive memory limitations

On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov wrote: > 2017-06-20 0:19 GMT+03:00 Joel Sherrill : > >> Check the value in gdb without loading it on a target. >> >> Gdb hello.exe >> >> p symbol >> > >> Since it is a constant, it should be as expected. If

Re: RSB Couverture-Qemu build queries

On 06/17/2017 10:28 AM, Cillian O'Donnell wrote: > On 16 June 2017 at 22:00, Jiri Gaisler wrote: >> Hi Cillian, >> >> the gaisler.org server is currently down due to a power problem last >> week. I am in the Caribbean at the moment so I can't fix it until >> Tuesday next week.

Re: RSB Couverture-Qemu build queries

On 19/06/2017 20:33, Cillian O'Donnell wrote: > On 18 June 2017 at 03:23, Chris Johns wrote: >> On 17/6/17 6:38 am, Joel Sherrill wrote: >>> On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell >> > wrote: >> Use '--trace

Re: RISC-V/HiFive memory limitations

2017-06-20 0:19 GMT+03:00 Joel Sherrill : > Check the value in gdb without loading it on a target. > > Gdb hello.exe > > p symbol > > Since it is a constant, it should be as expected. If it is, you have a > code loading issue. > Yes, it is 512 in gdb, as expected. So, is the

Re: RISC-V/HiFive memory limitations

Check the value in gdb without loading it on a target. Gdb hello.exe p symbol Since it is a constant, it should be as expected. If it is, you have a code loading issue. Is that value by any chance an instruction? On Jun 19, 2017 4:03 PM, "Denis Obrezkov" wrote: >

Re: RISC-V/HiFive memory limitations

Hi Denis, If you cscope this symbol you'll end up with the following: /** > * By default, use the minimum stack size requested by this port. > */ > #ifndef CONFIGURE_MINIMUM_TASK_STACK_SIZE > #define CONFIGURE_MINIMUM_TASK_STACK_SIZE CPU_STACK_MINIMUM_SIZE > #endif > This means if you, from

Re: [PATCH] bsps: Improve interrupt vector enable/disable API

- Ursprüngliche Mail - > Von: "Gedare Bloom" > An: "Sebastian Huber" > CC: "RTEMS Devel" > Gesendet: Montag, 19. Juni 2017 16:34:00 > Betreff: Re: [PATCH] bsps: Improve interrupt vector enable/disable API > On

Re: RTEMS-libbsd copyright question

On 19/06/17 08:57, Sichen Zhao wrote: I have a question about copyright in rtems-libbsd: i ported some usb driver files from FreeBSD, i modified somewhere in these files to suit with rtems-libbsd. Should i add my copyright in these file? This depends on your modifications. If you put only

[PATCH] bsps: Improve interrupt vector enable/disable API

Change bsp_interrupt_vector_enable() and bsp_interrupt_vector_disable() to not return a status code. Add bsp_interrupt_assert() and use it to validate the vector number in the vector enable/disable implementations. --- c/src/lib/libbsp/arm/beagle/irq.c | 12 +++---

Re: RTEMS-libbsd copyright question

Hello Sichen Zhao, Copyright applies to any new code that you personally author. The conventional wisdom is that if you make 3 or more lines of new code in a file, then you have expressed some original thoughts/ideas in the code and a copyright existss so you can/should add your name. Changing

Re: Valid interrupt vectors and the interrupt server

On Sun, Jun 18, 2017 at 9:59 PM, Chris Johns wrote: > On 18/06/2017 17:45, Christian Mauderer wrote: >> >> yes the interrupt server uses an pseudo interrupt on _every_ target: >> >> https://git.rtems.org/rtems/tree/c/src/lib/libbsp/shared/src/irq-server.c?id=ae359a9df#n31 > >

Re: RSB Couverture-Qemu build queries

On 18 June 2017 at 03:23, Chris Johns wrote: > On 17/6/17 6:38 am, Joel Sherrill wrote: >> >> >> On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell > > wrote: >> >> Hi, >> >> I am getting the RSB to build

RTEMS-libbsd copyright question

Hi all, I have a question about copyright in rtems-libbsd: i ported some usb driver files from FreeBSD, i modified somewhere in these files to suit with rtems-libbsd. Should i add my copyright in these file? Besides, I also modified some files in the rtemsbsd folder,. Should i add my copyright