Re: [GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library

On 9/6/18 10:00 am, Joel Sherrill wrote: > On Thu, Jun 7, 2018, 9:01 PM Chris Johns > wrote: > > and what > > discussions we need to have to decide between the "bundled kernel.so > approach" > > (the one implemented here) vs. the "FreeBSD loader.efi+hello.exe"

Re: [GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library

On Thu, Jun 7, 2018, 9:01 PM Chris Johns wrote: > On 08/06/2018 01:50, Amaan Cheval wrote: > > > > Joel, Chris, I'd appreciate guidance on what I ought to work on next > > I would like to see the focus on the kernel context switcher, FPU support, > and > then interrupts so we have the basic drive

Re: [PATCH 3/6] shgen: Import from RTEMS

On 9/6/18 9:48 am, Joel Sherrill wrote: > On Fri, Jun 8, 2018 at 6:28 PM, Chris Johns > wrote: > > On 8/6/18 10:32 pm, Gedare Bloom wrote: > > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns > wrote: > >> On 07/06/2018 16:11, Sebasti

Re: [GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library

On 9/6/18 2:39 am, Amaan Cheval wrote: > On Fri, Jun 8, 2018 at 7:31 AM, Chris Johns wrote: >> On 08/06/2018 01:50, Amaan Cheval wrote: >>> >>> Joel, Chris, I'd appreciate guidance on what I ought to work on next >> >> I would like to see the focus on the kernel context switcher, FPU support, >>

Re: [PATCH 3/6] shgen: Import from RTEMS

On Fri, Jun 8, 2018 at 6:28 PM, Chris Johns wrote: > On 8/6/18 10:32 pm, Gedare Bloom wrote: > > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: > >> On 07/06/2018 16:11, Sebastian Huber wrote: > >>> On 07/06/18 07:53, Chris Johns wrote: > On 07/06/2018 15:39, Sebastian Huber wrote: > >

Re: [PATCH 3/6] shgen: Import from RTEMS

On 8/6/18 10:32 pm, Gedare Bloom wrote: > On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: >> On 07/06/2018 16:11, Sebastian Huber wrote: >>> On 07/06/18 07:53, Chris Johns wrote: On 07/06/2018 15:39, Sebastian Huber wrote: > Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a

Re: [PATCH] Fix --show-commands.

Am 08.06.2018 um 15:35 schrieb Chris Johns: > > >> On 8 Jun 2018, at 4:21 pm, Christian Mauderer >> wrote: >> >>> Am 06.06.2018 um 09:48 schrieb Christian Mauderer: >>> In the current version of libbsd, if the --show-commands option is used, >>> the cwd is passed as a Nod3. Popen does not work

Re: [GSoC - x86_64 BSP] Using fPIC to compile RTEMS as a shared library

On Fri, Jun 8, 2018 at 7:31 AM, Chris Johns wrote: > On 08/06/2018 01:50, Amaan Cheval wrote: >> >> Joel, Chris, I'd appreciate guidance on what I ought to work on next > > I would like to see the focus on the kernel context switcher, FPU support, and > then interrupts so we have the basic drivers

Re: [PATCH 3/6] shgen: Import from RTEMS

I had an email some time ago with the developer of the SuperH FPGA implementation (http://j-core.org/). Personally, I was close to putting it on the deprecate list about the time I read about that project. Seeing there would be an open implementation seemed a reason to give it a lease on life. I

Re: [PATCH] Fix --show-commands.

> On 8 Jun 2018, at 4:21 pm, Christian Mauderer > wrote: > >> Am 06.06.2018 um 09:48 schrieb Christian Mauderer: >> In the current version of libbsd, if the --show-commands option is used, >> the cwd is passed as a Nod3. Popen does not work with that. Therefore >> create a string from cwd if

Re: [PATCH] Fix --show-commands.

On Fri, Jun 8, 2018 at 2:21 AM, Christian Mauderer wrote: > Am 06.06.2018 um 09:48 schrieb Christian Mauderer: >> In the current version of libbsd, if the --show-commands option is used, >> the cwd is passed as a Nod3. Popen does not work with that. Therefore >> create a string from cwd if it isn'

Re: [PATCH 3/6] shgen: Import from RTEMS

On Thu, Jun 7, 2018 at 10:19 PM, Chris Johns wrote: > On 07/06/2018 16:11, Sebastian Huber wrote: >> On 07/06/18 07:53, Chris Johns wrote: >>> On 07/06/2018 15:39, Sebastian Huber wrote: Corresponding RTEMS commit is 75933d5d25cd50f80162b7a0d2f66a5534e1763f. Update #3443. --- >

Re: configure/make with multiple jobs error?

On Thu, Jun 7, 2018 at 10:04 PM, Chris Johns wrote: > On 08/06/2018 04:42, Gedare Bloom wrote: >> OK, and I concur with your assessment. It worked a couple months ago. >> I might try to bisect if I have time. I would bet something in our >> scripts that changed during the source code reorg causes