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 e

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 wr

Re: [PATCH 01/25] score: Add Blackfin CPU architecture group

On 30/03/2019 00:12, Chris Johns wrote: Hi, Thank you for these changes. It is nice to see doxygen support being improved. Could I please suggest the first line of the commit message has `doxygen` in it, such as 'doxygen: score: Add Blackfin CPU architecture group' so a compact git log report o

Re: GSoC 2019

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 easier to work with the Git mirrors if you want to track the upstream.

Re: GSoC 2019

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. On Tue, 2 Apr, 2019, 10:24 AM Sebastian Huber, < sebastian.hu...@embedded-brains.de> wrote: > On 02/04/2019 05:44, Vaibhav Gupta

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

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 the rtems_interrupt_lock_* API and not the internal API. -- Sebast

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

On 31/03/2019 16:33, Hesham Almatary wrote: - if (RISCV_CONSOLE_IS_COMPATIBLE(compat, compat_len, "ns16750")) { -ctx->has_precision_clock_synthesizer = true; This change should be not a part of this patch and merged with patch 2. -- Sebastian Huber, embedded brains GmbH Address :

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

On 31/03/2019 16:33, 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 need to query interrupts. --- bsps/riscv/riscv/console/consol

Re: GSoC 2019

On 02/04/2019 05:44, Vaibhav Gupta wrote: - getting familiar with SVN (for FreeBSD) and CVS (for NetBSD). Both project have Git mirrors. I would use them. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89

GSoC 2019

Hello, . I am not able to get much active on devel these days as my mid-semester exams are going on (April 1-6). I have already mentioned this in my proposal under the heading, "Conflict of Interests". . My proposal- ​ https://docs.google.com/document/d/1NLbcFdHwWTEAismvz0E_C07Oos_4p6Y3IRGcE8fu

Re: GSoC Proposal : BeagleBoard project

On 2/4/19 12:06 am, Sebastian Huber wrote: > On 31/03/2019 03:57, Chris Johns wrote: >> On 31/3/19 5:05 am, Vijay Kumar Banerjee wrote: >>> On Sat, Mar 30, 2019 at 5:09 PM Gedare Bloom >> > wrote: >>> >>> Remember you can submit your "Final" proposal many times on GSoC

Re: rtems-libbsd build error

Am 01.04.19 um 16:38 schrieb Vijay Kumar Banerjee: > Doing a make for all, I'm getting this not found error ... Just a note: The make for all shouldn't be necessary. But if you do it please have a very detailed look at what is changed. It should be nothing except the things you added. > .

Re: rtems-libbsd build error

Doing a make for all, I'm getting this not found error ... make: freebsd-org/contrib/libpcap/gen_version_header.sh: Command not found make: *** [Makefile.todo:277: freebsd/contrib/libpcap/pcap_version.h] Error 127 . But it successefully builds the .m files into .c and .h f

Re: RTEMS on ARMv8

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, > > > > On 27/03/2019 19:11, Jeff Kubascik wrote: > >> Hello, > >> >

Re: rtems-libbsd build error

Am 01.04.19 um 15:29 schrieb Vijay Kumar Banerjee: [...] (I removed some of the discussion to make it more readable) > > If you use the fb and framebuffer headers from RTEMS, you will get an > RTEMS interface. The RTEMS based console code will work fine. But it > might would be the s

Re: RTEMS on ARMv8

On Mon, Apr 1, 2019 at 7:54 AM Jeff Kubascik wrote: > On 3/28/2019 8:00 AM, Sebastian Huber wrote: > > Hello Jeff, > > > > On 27/03/2019 19:11, Jeff Kubascik wrote: > >> Hello, > >> > >> I am interested in porting RTEMS to run as a Xen guest on our distro > for the > >> Xilinx Zynq UltraScale+ MP

Re: rtems-libbsd build error

On Thu, Mar 21, 2019 at 10:21 PM Christian Mauderer wrote: > Am 21.03.19 um 15:36 schrieb Vijay Kumar Banerjee: > > > > On Wed, 20 Mar 2019 at 01:52, Christian Mauderer > > wrote: > > > > Am 19.03.19 um 20:37 schrieb Vijay Kumar Banerjee: > > > > > > > >

Re: GSoC Proposal : BeagleBoard project

On 31/03/2019 03:57, Chris Johns wrote: On 31/3/19 5:05 am, Vijay Kumar Banerjee wrote: On Sat, Mar 30, 2019 at 5:09 PM Gedare Bloom mailto:ged...@rtems.org>> wrote: Remember you can submit your "Final" proposal many times on GSoC site. I made a few comments just regarding the 'public

Re: RTEMS on ARMv8

On 3/28/2019 8:00 AM, Sebastian Huber wrote: > Hello Jeff, > > On 27/03/2019 19:11, Jeff Kubascik wrote: >> Hello, >> >> I am interested in porting RTEMS to run as a Xen guest on our distro for the >> Xilinx Zynq UltraScale+ MPSoC. The MPSoC has an ARM Cortex-A53 processor, >> which >> is based o