Displaying 5 results from an estimated 5 matches for "char8".
Did you mean:
char
2010 Aug 14
4
\" character in folder name results in strange LIST
Hi Timo,
>> * LIST (\HasNoChildren) "/" "folder1"
>> * LIST (\HasNoChildren) "/" "folder2"
>> * LIST (\HasNoChildren) "/" {9}
>> six"wafer
>> . OK List completed.
>>
>> Note the {9} length of the following real folder name. Is this normal
>> handling of special folder names ?
>Yes.
Well,
2013 Nov 26
3
[PATCH v3 3/8] OvmfPkg: define EFI_XEN_OVMF_INFO and extend XenInfo
...KIND, EITHER EXPRESS OR IMPLIED.
+
+**/
+
+#ifndef __XEN_H__
+#define __XEN_H__
+
+#include <Uefi/UefiBaseType.h>
+
+// Physical address of OVMF info
+#define OVMF_INFO_PHYSICAL_ADDRESS 0x00001000
+
+// This structure must match the definition on Xen side
+#pragma pack(1)
+typedef struct {
+ CHAR8 Signature[14]; // XenHVMOVMF\0
+ UINT8 Length; // Length of this structure
+ UINT8 Checksum; // Set such that the sum over bytes 0..length == 0
+ //
+ // Physical address of an array of TablesCount elements.
+ //
+ // Each element contains the physical address of a BIOS table.
+...
2002 Apr 14
4
Visual Studio .NET
Hi`
we recently switched to using Visual Studio .NET and now I get a crash
inside Ogg Vorbis unless I recompile Ogg Vorbis itself with Visual Studio
.NET. Are there any known issues like that? If possible I'd like to use the
official binaries.
-- Daniel, Epic Games Inc.
<p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To
2002 Apr 14
4
Visual Studio .NET
Hi`
we recently switched to using Visual Studio .NET and now I get a crash
inside Ogg Vorbis unless I recompile Ogg Vorbis itself with Visual Studio
.NET. Are there any known issues like that? If possible I'd like to use the
official binaries.
-- Daniel, Epic Games Inc.
<p>--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To
2013 Apr 29
1
CATENATE doesn't support literal+ url
...(SP cat-part) ")"
cat-part = text-literal / url
url = "URL" SP astring
RFC 3501 section 9:
astring = 1*ASTRING-CHAR / string
string = quoted / literal
RFC 2088 section 4:
literal ::= "{" number ["+"] "}" CRLF *CHAR8