[Xen-changelog] [xen master] docs: EFI configuration file must be ASCII type

[patchbot@xxxxxxx]

commit 204c7a873fbe1ac62a61c93babb858635dfe9c3a
Author:     Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
AuthorDate: Thu Oct 23 10:24:19 2014 +0200
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Thu Oct 23 10:24:19 2014 +0200

    docs: EFI configuration file must be ASCII type
    
    Currently Xen can only read the configuration file if it is in ASCII
    format. If it is in CHAR16 or CHAR8 it will choke. One way to verify
    this is to use 'file':
    
    xen.cfg:        ASCII text
    xen-char16.cfg: Little-endian UTF-16 Unicode text, with CRLF, CR line 
terminators
    
    The latter is no good.
    
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
---
 docs/misc/efi.markdown |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/docs/misc/efi.markdown b/docs/misc/efi.markdown
index ad8da93..5e48aa3 100644
--- a/docs/misc/efi.markdown
+++ b/docs/misc/efi.markdown
@@ -34,7 +34,8 @@ The configuration file consists of one or more sections 
headed by a section
 name enclosed in square brackets, with individual values specified in each
 section. A section named `[global]` is treated specially to allow certain
 settings to apply to all other sections (or to provide defaults for certain
-settings in case individual sections don't specify them). A typical file would
+settings in case individual sections don't specify them). This file (for now)
+needs to be of ASCII type and not e.g. UTF-8 or UTF-16. A typical file would
 thus look like this (`#` serving as comment character):
 
     **************************example begin******************************
--
generated by git-patchbot for /home/xen/git/xen.git#master

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog