On 11/18/2013 05:47 PM, David F. wrote:
> Thanks - I found the grub option for set debug= (I couldn't use all
> since it would lock up - but used disk,efidisk,modules,loader) and can
> see it reads 0x100 sectors from sector 0x500 then reads 0x4C00 sectors
> from sector 0x600. So perhaps that's it.
On 08/05/2013 02:41 PM, Borislav Petkov wrote:
> On Mon, Aug 05, 2013 at 02:37:08PM -0700, H. Peter Anvin wrote:
>> All of this would be a non-problem if there weren't buggy
>> implementations which can't run *without* SetVirtualAddressMap().
>
> Oh, you mean,
On 08/05/2013 11:12 AM, Borislav Petkov wrote:
> On Mon, Aug 05, 2013 at 08:50:17AM -0700, Andrew Fish wrote:
>> AFAICT EFI pre-dates kexec merge into mainline by a number of years as
>> SetVirtualaddressMap() was part of EFI 1.0 (previous millennium)
>
> Ok, fair enough.
>
>> The EFI to UEFI con
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
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
address and length filled in at runtime.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
Minimize network downtime and maximize team effectivenes
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
mapped to the PCI so that the upper subset of
>this region is aliased to 16 Mbytes minus 256-Kbyte range.
>
That is presumably a 286 compatibility hack -- the 286 had 24 address
lines. I doubt anyone gives a hoot about it, and neither EDK2 nor
SeaBIOS should care.
-hpa
--
H. Pet
On 02/14/2013 12:41 PM, Laszlo Ersek wrote:
>
> ). cpu_reset() [target-i386/helper.c] sets CS:IP to f000:fff0, which is
> the exact address of... reset_vector() in SeaBIOS.
>
This would be a bug, but it isn't quite true.
If you look at x86_cpu_reset() you will note that it sets the code
segment
On 02/12/2013 04:20 AM, David Woodhouse wrote:
> On Tue, 2013-02-12 at 11:11 +, Grant Likely wrote:
>>
>>> This mismatch generally makes sharing changes/trees more difficult,
>>> and thus is a point in favor of git vs. git-svn.
>>
>> s/more difficult/impossible/ The git mirrors become basicall
On 01/28/2013 03:31 PM, David Woodhouse wrote:
> + if (Bp->hdr.version >= 0x20c && Bp->hdr.handover_offset &&
> + (Bp->hdr.xloadflags & sizeof(long))) {
Cute. I didn't even realize this was the bit assignment ;)
-hpa
--
On 01/09/2013 02:05 PM, H. Peter Anvin wrote:
> On 01/09/2013 02:02 PM, Jordan Justen wrote:
>> On Wed, Jan 9, 2013 at 11:12 AM, David Woodhouse wrote:
>>> We're supposed to zero everything in the kernel bootparams that we don't
>>> explicitly initialise, o
On 01/09/2013 02:02 PM, Jordan Justen wrote:
> On Wed, Jan 9, 2013 at 11:12 AM, David Woodhouse wrote:
>> We're supposed to zero everything in the kernel bootparams that we don't
>> explicitly initialise, other than the setup_header from 0x1f1 onwards
>> for a precisely defined length, which is co
On 01/09/2013 01:35 PM, David Woodhouse wrote:
> On Wed, 2013-01-09 at 13:24 -0800, Jordan Justen wrote:
>>
>> This push won't assemble. ("Invalid instruction operands")
>>
>> There might be a way to get masm to assemble that instruction, but I
>> don't know the magic syntax.
>
> Hm. it works for
On 01/08/2013 04:33 PM, David Woodhouse wrote:
> On Tue, 2013-01-08 at 16:21 -0800, Jordan Justen wrote:
>>
>>> MASM is really so broken it doesn't handle mixed-mode programming at
>> all?
>>
>> I believe this is the case for 64-bit.
>> http://en.wikipedia.org/wiki/Microsoft_Macro_Assembler
>>
>> "
isn't MASM, though; it is somewhat similar but far from identical.
For example, in MASM:
mov eax,foo
... can be either an immediate or a memory reference depending on
exactly how "foo" is declared.
There is an assembler called WASM/JWASM that is available for Linux
w
16 matches
Mail list logo
