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

Minor update: I'll work on Chris' suggestion of using FreeBSD's loader.efi and having that load our static hello.exe - it ought to be a quicker test that way. On Sun, Jun 10, 2018 at 9:34 PM Amaan Cheval wrote: > > On Sun, Jun 10, 2018 at 12:38 AM Joel Sherrill wrote: > > > > > > > > On Fri, Jun

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

On Sun, Jun 10, 2018 at 12:38 AM Joel Sherrill wrote: > > > > On Fri, Jun 8, 2018 at 7:45 PM, Chris Johns wrote: >> >> 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

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

On Sat, Jun 9, 2018 at 5:26 AM Chris Johns wrote: > > 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

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

On Fri, Jun 8, 2018 at 7:45 PM, Chris Johns wrote: > 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" > > >

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

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

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: [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

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

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 we need like a tick interrupt running. This assumes the

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

Chris, I've blogged a summary of the 2 approaches we can take in integrating gnu-efi in case you missed the discussions earlier, btw. The FreeBSD approach isn't as fleshed out, but I'll let you all know what I find there. https://blog.whatthedude.com/post/gnu-efi-kernel-so/ On Wed, Jun 6, 2018

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

I don't know yet, but I'll look into it. I'll pause the "hello.efi" approach work until we settle on a direction, yes? For now, primarily improving the stub, looking into the FreeBSD ld-elf.so, etc. Sound good? On Wed, Jun 6, 2018, 1:01 PM Chris Johns wrote: > On 6/6/18 5:22 pm, Amaan Cheval

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

On 6/6/18 5:22 pm, Amaan Cheval wrote: > On Wed, Jun 6, 2018 at 12:45 PM, Chris Johns wrote: >> On 6/6/18 5:06 pm, Amaan Cheval wrote: >>> On Wed, Jun 6, 2018 at 6:55 AM, Chris Johns wrote: On 4/6/18 7:49 pm, Amaan Cheval wrote: > Please let me know if that approach doesn't make sense -

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

On Wed, Jun 6, 2018 at 12:45 PM, Chris Johns wrote: > On 6/6/18 5:06 pm, Amaan Cheval wrote: >> On Wed, Jun 6, 2018 at 6:55 AM, Chris Johns wrote: >>> On 4/6/18 7:49 pm, Amaan Cheval wrote: Please let me know if that approach doesn't make sense - given that there is no dynamic loader

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

On 6/6/18 5:06 pm, Amaan Cheval wrote: > On Wed, Jun 6, 2018 at 6:55 AM, Chris Johns wrote: >> On 4/6/18 7:49 pm, Amaan Cheval wrote: >>> Please let me know if that approach doesn't make sense - given that >>> there is no dynamic loader in the RTEMS kernel as far as I know, >> >> There is a

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

On Wed, Jun 6, 2018 at 6:55 AM, Chris Johns wrote: > On 4/6/18 7:49 pm, Amaan Cheval wrote: >> Please let me know if that approach doesn't make sense - given that >> there is no dynamic loader in the RTEMS kernel as far as I know, > > There is a dynamic loader in RTEMS called libdl. It is not

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

On 4/6/18 7:49 pm, Amaan Cheval wrote: > Please let me know if that approach doesn't make sense - given that > there is no dynamic loader in the RTEMS kernel as far as I know, There is a dynamic loader in RTEMS called libdl. It is not based around the ELF standard loader used for shared libraries

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

On Tue, Jun 5, 2018 at 4:27 PM, Amaan Cheval wrote: > Hi! Thanks for the guidance, both of you! I think we're quite close > now to integrating gnu-efi in and finally having the stub port boot as > a UEFI application image. All the test exe's generated on my local > tree are now dynamic

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

Hi! Thanks for the guidance, both of you! I think we're quite close now to integrating gnu-efi in and finally having the stub port boot as a UEFI application image. All the test exe's generated on my local tree are now dynamic libraries, so both Newlib and crtbeginS/crtendS issues have been

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

On Mon, Jun 4, 2018 at 5:44 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > - Am 4. Jun 2018 um 12:20 schrieb Amaan Cheval amaan.che...@gmail.com: > > > That's a good idea. That way based on the multilib variant, Newlib would > be > > compiled using fPIC, yes? > > Yes.

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

- Am 4. Jun 2018 um 12:20 schrieb Amaan Cheval amaan.che...@gmail.com: > That's a good idea. That way based on the multilib variant, Newlib would be > compiled using fPIC, yes? Yes. > > Then I could simply figure out how to solve the crtbegin and crtend dilemma > (which I believe should

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

That's a good idea. That way based on the multilib variant, Newlib would be compiled using fPIC, yes? Then I could simply figure out how to solve the crtbegin and crtend dilemma (which I believe should be easier), and use those to have a dynamic/shared RTEMS kernel + user application. If that

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

Hello Amaan, can't you add a new multilib variant which includes -fPIC to the GCC configuration for RTEMS? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel