Re: [PATCH 3/4] bsps/riscv: UART - Comment code that queries UART interrupts

On 2/4/19 10:08 pm, Hesham Almatary wrote: > On Sun, 31 Mar 2019 at 22:50, Chris Johns wrote: >> >> On 1/4/19 1:33 am, Hesham Almatary wrote: >>> * Different RISC-V DTBs use different names for UART interrupts such as >>> "interrupts" and "interrupts-extended", so it is not portable. >>> *

Fwd: [GSoC Mentors] Season of Docs is now inviting organizations to apply

What do you all think? -- Forwarded message - From: 'sttaylor' via Google Summer of Code Mentors List < google-summer-of-code-mentors-l...@googlegroups.com> Date: Tue, Apr 2, 2019 at 3:31 PM Subject: [GSoC Mentors] Season of Docs is now inviting organizations to apply To: Google

Re: RTEMS on ARMv8

On Tue, Apr 2, 2019 at 8:34 AM Joel Sherrill wrote: > > > > On Tue, Apr 2, 2019, 7:21 AM Sebastian Huber > wrote: >> >> On 02/04/2019 14:15, Jeff Kubascik wrote: >> > How capable is the device tree support in RTEMS? I did notice some device >> > tree >> > code in the IMX BSP layer, but it

Re: Adding PRU support to BeagleBone during GSoC

On Tue, Apr 2, 2019 at 11:23 AM Nils Hölscher wrote: > Hi, > > Here is my proof for the starting guide. > Add yourself to the GSoC 2019 page. > > And I tried to answer your questions in the ticket. > +1 > > Best, > Nils > > On Tue, 2 Apr 2019 at 17:45, Joel Sherrill wrote: > >> >> >> On

Re: Adding PRU support to BeagleBone during GSoC

On Tue, Apr 2, 2019 at 10:17 AM Nils Hölscher wrote: > Hi, > > I would like participate @GSoC with the RTEMS community and wrote a > proposal to bring Programmable Real-Time Units (PRU) support to the > BeagleBone. > I don't know much about the PRU. I see TI has a compiler for it. How does the

Fwd: [RFC/RFA] Obsolete Cell Broadband Engine SPU targets

Hi We knew this was coming. My recollection is that we have a single BSP this would impact. But that has already been impacted by SPU being split into a separate gcc target post GCC 7. And that has not been addressed yet anyway. What's the plan for SPU? -- Forwarded message -

Re: RTEMS on ARMv8

On Tue, Apr 2, 2019, 7:21 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 02/04/2019 14:15, Jeff Kubascik wrote: > > How capable is the device tree support in RTEMS? I did notice some > device tree > > code in the IMX BSP layer, but it appeared to reference fixed nodes. >

Re: RTEMS on ARMv8

On 02/04/2019 14:15, Jeff Kubascik wrote: How capable is the device tree support in RTEMS? I did notice some device tree code in the IMX BSP layer, but it appeared to reference fixed nodes. Does RTEMS perform driver probing based on the device tree? The device tree support in RTEMS is quite

Re: RTEMS on ARMv8

On 4/2/2019 2:35 AM, Sebastian Huber wrote: > On 02/04/2019 08:13, Sebastian Huber wrote: >> On 01/04/2019 16:08, Jeff Kubascik wrote: >>> On 4/1/2019 9:45 AM, Joel Sherrill wrote: On Mon, Apr 1, 2019 at 7:54 AM Jeff Kubascik >>> > wrote:

Re: [PATCH] Remove pcap_version.h

Thanks, committed. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine

Re: rtems-libbsd linking error

On 02/04/2019 13:07, Vijay Kumar Banerjee wrote: Hello, I'm getting a linking error in epoch01.exe while trying to ./waf the current master. rtems-libbsd $>./waf -j1 ... [1774/1883] Linking build/arm-rtems5-beagleboneblack-default/epoch01.exe

Re: [PATCH 4/4] bsps/riscv: HTIF - Use 32-bit HTIF syscalls on RV32

On Tue, 2 Apr 2019 at 06:16, Sebastian Huber wrote: > > > > On 31/03/2019 16:33, Hesham Almatary wrote: > > +static ISR_lock_Control htif_lock; > > +static ISR_lock_Context htif_lock_context; > > The lock context must be unique for each caller, so please use a stack > variable for it. Please use

Re: [PATCH 3/4] bsps/riscv: UART - Comment code that queries UART interrupts

On Sun, 31 Mar 2019 at 22:50, Chris Johns wrote: > > On 1/4/19 1:33 am, Hesham Almatary wrote: > > * Different RISC-V DTBs use different names for UART interrupts such as > > "interrupts" and "interrupts-extended", so it is not portable. > > * polling functions are currently used, so there is no

rtems-libbsd linking error

Hello, I'm getting a linking error in epoch01.exe while trying to ./waf the current master. rtems-libbsd $>./waf -j1 ... [1774/1883] Linking build/arm-rtems5-beagleboneblack-default/epoch01.exe /home/lunatic/development/rtems/5/lib/gcc/arm-rtems5/7.4.0/../../../../arm-rtems5/bin/ld: cannot find

[PATCH 2/2] bsps/riscv: HTIF - Use 32-bit HTIF syscalls on RV32

HTIF devices are not supported on RV32, so proxy a write system call This syncs HTIF Console with riscv-pk (proxy kernel) to use 32-bit HTIF syscalls on RV32 instead of 64-bit commands that are not atomic. --- bsps/riscv/riscv/console/htif.c | 59 + 1 file

[PATCH 1/2] bsps/riscv: UART - Read reg-shift from DTB to properly set/get registers

--- bsps/riscv/riscv/console/console-config.c | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/bsps/riscv/riscv/console/console-config.c b/bsps/riscv/riscv/console/console-config.c index 464b4b0e26..04d0b28361 100644 ---

Re: RTEMS on ARMv8

On 02/04/2019 08:13, Sebastian Huber wrote: On 01/04/2019 16:08, Jeff Kubascik wrote: On 4/1/2019 9:45 AM, Joel Sherrill wrote: On Mon, Apr 1, 2019 at 7:54 AM Jeff Kubascik > wrote: On 3/28/2019 8:00 AM, Sebastian Huber wrote: > Hello Jeff,

Re: GSoC 2019

On Tue, Apr 2, 2019 at 11:05 AM Sebastian Huber wrote: > > On 02/04/2019 07:28, Vaibhav Gupta wrote: > > I had this discussion under comments section in my drafted proposal. > > Aditya said we will be using the Version control, they are using, to > > figure out the origin of file. > > It is much

Re: RTEMS on ARMv8

On 01/04/2019 16:08, Jeff Kubascik wrote: On 4/1/2019 9:45 AM, Joel Sherrill wrote: On Mon, Apr 1, 2019 at 7:54 AM Jeff Kubascik mailto:jeff.kubas...@dornerworks.com>> wrote: On 3/28/2019 8:00 AM, Sebastian Huber wrote: > Hello Jeff, > > On 27/03/2019 19:11, Jeff Kubascik