On 04/04/2013 05:44 PM, Tim Lewis wrote:
> My point was: wouldn't it be easier to ship with an ACPI table that is not
> AML. For example, like IBST for iSCSI, where a table has a name and the data
> portion is just the start and size. As a point of reference, please see
> Appendix O of the UEFI
d at least 5 different ways (Zero, UINT8, UINT16, UINT32, UINT64).
Tim
-Original Message-
From: H. Peter Anvin [mailto:h...@zytor.com]
Sent: Thursday, April 04, 2013 5:39 PM
To: Tim Lewis
Cc: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Boot to ISO image in volatile memory
On 04/
On 04/04/2013 05:03 PM, Andrew Fish wrote:
>
> I think the tricky part is telling the OS that this memory range has special
> properties. You want to treat it like EFIACPIReclaimMemory, as the OS could
> convert the range to pageable memory. If you make the memory
> EfiRuntimeServicesData then
On 04/04/2013 04:54 PM, Tim Lewis wrote:
> Or an EFI System Configuration table (which uses a GUID to identify it) Not
> sure about SSDT, since that would require an AML interpreter.
>
> Tim
The OS has an AML interpreter already. The SSDT can be pre-generated
with only the address and length
dependent?
Thanks,
Andrew
> Tim
>
>
> -Original Message-
> From: H. Peter Anvin [mailto:h...@zytor.com]
> Sent: Thursday, April 04, 2013 4:50 PM
> To: edk2-devel@lists.sourceforge.net
> Cc: Tim Lewis
> Subject: Re: [edk2] Boot to ISO image in volatile mem
Cc: Tim Lewis
Subject: Re: [edk2] Boot to ISO image in volatile memory
On 04/04/2013 12:27 PM, Tim Lewis wrote:
> Produce an instance of BLOCK_IO protocol which returns pieces of the
> in-memory image. Then perform a ConnectController() on that handle, which
> should cause a DI
Thanks, Jordan! I will look at your code tomorrow morning; it will
probably help me out a lot.
On Thu, Apr 4, 2013 at 6:32 PM, Jordan Justen wrote:
> On Thu, Apr 4, 2013 at 4:15 PM, Andrew Fish wrote:
> > On Apr 4, 2013, at 3:50 PM, Thomas Rognon wrote:
> >
> > I found this on the internet,
are trying to boot an OS, then you have to figure out how to
>>> convince how to convince that OS to continue to use that driver once it
>>> reaches the hand-off point in boot, because it then requires a native OS
>>> driver to continue to access your ISO.
>>&g
On 04/04/2013 12:27 PM, Tim Lewis wrote:
> Produce an instance of BLOCK_IO protocol which returns pieces of the
> in-memory image. Then perform a ConnectController() on that handle, which
> should cause a DISK_IO and SIMPLE_FILE_SYSTEM to be mounted automatically.
>
> Then, you use the file syst
On Thu, Apr 4, 2013 at 4:15 PM, Andrew Fish wrote:
> On Apr 4, 2013, at 3:50 PM, Thomas Rognon wrote:
>
> I found this on the internet,
> The UEFI adaptation of ElTorito results in mapping image offset 14800-A27FF
> as a FAT file system, and executing file EFI/BOOT/BOOTX64.efi in the 64-bit
> UEF
t;
>>
>>
>> If you are trying to boot an OS, then you have to figure out how to convince
>> how to convince that OS to continue to use that driver once it reaches the
>> hand-off point in boot, because it then requires a native OS driver to
>> continue to
point in boot, because it then requires a native OS
>> driver to continue to access your ISO.
>>
>> ** **
>>
>> Tim****
>>
>> ** **
>>
>> *From:* Thomas Rognon [mailto:tcrog...@gmail.com]
>> *Sent:* Thursday, April 04, 2013 1:31 PM
nt: Thursday, April 04, 2013 1:31 PM
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] Boot to ISO image in volatile memory
>
>
>
> Thanks! That gives me a great start. I'm new to a lot of this stuff,
> though, so the steps you outlined will be tough
t;
> ** **
>
> *From:* Thomas Rognon [mailto:tcrog...@gmail.com]
> *Sent:* Thursday, April 04, 2013 1:31 PM
> *To:* edk2-devel@lists.sourceforge.net
> *Subject:* Re: [edk2] Boot to ISO image in volatile memory
>
> ** **
>
> Thanks! That gives me a great start. I&#
@lists.sourceforge.net
Subject: Re: [edk2] Boot to ISO image in volatile memory
Thanks! That gives me a great start. I'm new to a lot of this stuff, though,
so the steps you outlined will be tough for me without guidance. Is there any
UEFI optical drive code floating around the internet some
be a few more standard boot
> items I may be forgetting, but that’s about it.
>
> ** **
>
> Tim
>
> ** **
>
> *From:* Thomas Rognon [mailto:tcrog...@gmail.com]
> *Sent:* Thursday, April 04, 2013 12:21 PM
> *To:* edk2-devel@lists.sourceforge.net
> *Subject:* [e
devel@lists.sourceforge.net
Subject: [edk2] Boot to ISO image in volatile memory
Let's say I'm running a UEFI_APPLICATION called IsoBootTest.efi and I have an
ISO image in volatile memory and I have the start address and size of the ISO
image. Can I boot the ISO image? If so, can so
Let's say I'm running a UEFI_APPLICATION called IsoBootTest.efi and I have
an ISO image in volatile memory and I have the start address and size of
the ISO image. Can I boot the ISO image? If so, can someone give me a
hint on how I would do it? (If it makes any difference, I'm using UDK2010.)
T
18 matches
Mail list logo
