On Wed, May 30, 2018 at 4:30 AM, Joel Sherrill wrote:
>
>
> On Tue, May 29, 2018 at 11:26 AM, Amaan Cheval
> wrote:
>>
>> On Tue, May 29, 2018 at 9:28 PM, Amaan Cheval
>> wrote:
>> > Noted, thanks a ton for the details! Unrelated to the topic at hand,
>> > but out of interest, is this the only
On Tue, May 29, 2018 at 11:26 AM, Amaan Cheval
wrote:
> On Tue, May 29, 2018 at 9:28 PM, Amaan Cheval
> wrote:
> > Noted, thanks a ton for the details! Unrelated to the topic at hand,
> > but out of interest, is this the only reading material for further
> > details?
On Tue, May 29, 2018 at 9:28 PM, Amaan Cheval wrote:
> Noted, thanks a ton for the details! Unrelated to the topic at hand,
> but out of interest, is this the only reading material for further
> details? http://ceur-ws.org/Vol-1697/EWiLi16_12.pdf
>
> In brief: My tests for keeping a libfake.a
Noted, thanks a ton for the details! Unrelated to the topic at hand,
but out of interest, is this the only reading material for further
details? http://ceur-ws.org/Vol-1697/EWiLi16_12.pdf
In brief: My tests for keeping a libfake.a (compiled without -fpic)
and a loader.so with a user-appXYZ.c have
On Fri, May 25, 2018, 12:11 PM Amaan Cheval wrote:
> Hey! Could you link me to some code that you used for the Deos setup
> you mentioned?
> My understanding is that the -shared option can link static archives
> to create a "shared" library in the sense that it doesn't
Hey! Could you link me to some code that you used for the Deos setup
you mentioned?
My understanding is that the -shared option can link static archives
to create a "shared" library in the sense that it doesn't include the
usual crt0 runtime environment and whatnot, but the code within is
still
On Fri, May 25, 2018, 11:15 AM Amaan Cheval wrote:
> Hey!
>
> Skippable details about how FreeBSD handles the UEFI boot process!
>
>
>
> Having looked into it a bit more, my understanding of
Hey!
Skippable details about how FreeBSD handles the UEFI boot process!
Having looked into it a bit more, my understanding of how FreeBSD
handles this process is:
- They build a two-stage bootloader for EFI, called
On Sun, May 20, 2018, 12:10 PM Amaan Cheval wrote:
> On Sat, May 19, 2018 at 6:51 PM, Gedare Bloom wrote:
> > On Fri, May 18, 2018 at 5:53 PM, Joel Sherrill wrote:
> >>
> >>
> >> On Fri, May 18, 2018 at 3:24 PM, Amaan Cheval
On Sat, May 19, 2018 at 6:51 PM, Gedare Bloom wrote:
> On Fri, May 18, 2018 at 5:53 PM, Joel Sherrill wrote:
>>
>>
>> On Fri, May 18, 2018 at 3:24 PM, Amaan Cheval
>> wrote:
>>>
>>> Hi everyone!
>>>
>>> I've written a quick blog post
On Fri, May 18, 2018 at 5:53 PM, Joel Sherrill wrote:
>
>
> On Fri, May 18, 2018 at 3:24 PM, Amaan Cheval
> wrote:
>>
>> Hi everyone!
>>
>> I've written a quick blog post summarizing the options I've considered
>> to make the x86_64 port work with UEFI
On Fri, May 18, 2018 at 3:24 PM, Amaan Cheval
wrote:
> Hi everyone!
>
> I've written a quick blog post summarizing the options I've considered
> to make the x86_64 port work with UEFI firmware - the primary winner
> seems to be in my eyes to use "gnu-efi" and to add
Hi everyone!
I've written a quick blog post summarizing the options I've considered
to make the x86_64 port work with UEFI firmware - the primary winner
seems to be in my eyes to use "gnu-efi" and to add support for the
target "pei-x86-64" (aliased to "efi-app-x86_64") to
"x86_64-rtems5-objcopy"
13 matches
Mail list logo