On Thu, 17 May 2007, H. Peter Anvin wrote:
+Field name:kernel_version
+Type: read
+Offset/size: 0x20e/2
+Protocol: 2.00+
+
+ If set to a nonzero value, contains a pointer to a null-terminated
"nil-terminated"? "\0-terminated"?
Uh? That seems more than a little silly.
On Thu, 17 May 2007 16:30:44 -0700 Jeremy Fitzhardinge wrote:
> >>> + If set to a nonzero value, contains a pointer to a null-terminated
> >>>
> >>>
> >> "nil-terminated"? "\0-terminated"?
> >>
> >
> > Uh? That seems more than a little silly. Yes, I guess formally
> > speaking
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Given that we have already established littleendian byte order, it's the
>> same thing.
>>
>
> Well, not quite; mentioning the string form first creates an ambiguity.
> I'd express as something like: ``The magic number is 0x53726448
>
H. Peter Anvin wrote:
> Given that we have already established littleendian byte order, it's the
> same thing.
>
Well, not quite; mentioning the string form first creates an ambiguity.
I'd express as something like: ``The magic number is 0x53726448
(implicitly, stored little-endian), which
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> +Field name: boot_flag
>> +Type: read
>> +Offset/size:0x1fe/2
>> +Protocol: ALL
>> +
>> + Contains 0xAA55. This is the closest thing old Linux kernels have
>> + to a magic number.
>>
>
> Endianess? I guess a
H. Peter Anvin wrote:
> +Field name: boot_flag
> +Type:read
> +Offset/size: 0x1fe/2
> +Protocol:ALL
> +
> + Contains 0xAA55. This is the closest thing old Linux kernels have
> + to a magic number.
>
Endianess? I guess a blanket statement saying that all constants are
A number of items in the i386 boot documentation have been either
vague, outdated or hard to read. This text revision adds several more
examples, including a memory map for a modern kernel load. It also
adds a field-by-field detailed description of the setup header, and a
bootloader ID for Qemu.
A number of items in the i386 boot documentation have been either
vague, outdated or hard to read. This text revision adds several more
examples, including a memory map for a modern kernel load. It also
adds a field-by-field detailed description of the setup header, and a
bootloader ID for Qemu.
H. Peter Anvin wrote:
+Field name: boot_flag
+Type:read
+Offset/size: 0x1fe/2
+Protocol:ALL
+
+ Contains 0xAA55. This is the closest thing old Linux kernels have
+ to a magic number.
Endianess? I guess a blanket statement saying that all constants are
stored
Jeremy Fitzhardinge wrote:
H. Peter Anvin wrote:
+Field name: boot_flag
+Type: read
+Offset/size:0x1fe/2
+Protocol: ALL
+
+ Contains 0xAA55. This is the closest thing old Linux kernels have
+ to a magic number.
Endianess? I guess a blanket statement
H. Peter Anvin wrote:
Given that we have already established littleendian byte order, it's the
same thing.
Well, not quite; mentioning the string form first creates an ambiguity.
I'd express as something like: ``The magic number is 0x53726448
(implicitly, stored little-endian), which
Jeremy Fitzhardinge wrote:
H. Peter Anvin wrote:
Given that we have already established littleendian byte order, it's the
same thing.
Well, not quite; mentioning the string form first creates an ambiguity.
I'd express as something like: ``The magic number is 0x53726448
(implicitly,
On Thu, 17 May 2007 16:30:44 -0700 Jeremy Fitzhardinge wrote:
+ If set to a nonzero value, contains a pointer to a null-terminated
nil-terminated? \0-terminated?
Uh? That seems more than a little silly. Yes, I guess formally
speaking we're talking about
On Thu, 17 May 2007, H. Peter Anvin wrote:
+Field name:kernel_version
+Type: read
+Offset/size: 0x20e/2
+Protocol: 2.00+
+
+ If set to a nonzero value, contains a pointer to a null-terminated
nil-terminated? \0-terminated?
Uh? That seems more than a little silly. Yes,
14 matches
Mail list logo
