From: David Woodhouse <dwmw2@infradead.org>
To: Mike Waychison <mikew@google.com>
Cc: Matt Fleming <matt@console-pimps.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Tom Gundersen <teg@jklm.no>
Subject: Re: [PATCH 1/6] efi: move utf16 string functions to efi.h
Date: Wed, 10 Apr 2013 12:18:37 +0100 [thread overview]
Message-ID: <1365592717.3072.57.camel@shinybook.infradead.org> (raw)
In-Reply-To: <CAGTjWtCFSxJMKf=Xp+5MKLSb3qH4YpWVYYmUb6fkjwctMc1bDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Tue, 2013-04-09 at 15:00 -0700, Mike Waychison wrote:
> fwiw, I was tempted to rename these to ucs2_*() last time I was here.
We should definitely do that. The functions aren't implementing UTF-16.
Note that Windows *does* now implement UTF16 I think, but EFI still
claims to be UCS2 only.
If I interpret this correctly, the claim is basically that Windows was
"always" actually UTF16, but just never used any of the code points
where you'd be able to notice the difference:
http://blogs.msdn.com/b/michkap/archive/2005/05/11/416552.aspx
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-04-10 11:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:18 [PATCH 0/6] Chainsaw efivars.c Matt Fleming
2013-04-04 12:18 ` [PATCH 1/6] efi: move utf16 string functions to efi.h Matt Fleming
2013-04-09 22:00 ` Mike Waychison
2013-04-10 11:18 ` David Woodhouse [this message]
2013-04-04 12:18 ` [PATCH 2/6] efivars: Keep a private global pointer to efivars Matt Fleming
2013-04-09 22:07 ` Mike Waychison
2013-04-11 13:10 ` Matt Fleming
2013-04-04 12:18 ` [PATCH 3/6] efivars: efivar_entry API Matt Fleming
2013-04-10 15:25 ` Seiji Aguchi
2013-04-11 13:34 ` Matt Fleming
2013-04-04 12:18 ` [PATCH 4/6] efivars: Move pstore code into the new EFI directory Matt Fleming
2013-04-04 12:18 ` [PATCH 5/6] efivarfs: Move to fs/efivarfs Matt Fleming
2013-04-04 12:18 ` [PATCH 6/6] efi: split efisubsystem from efivars Matt Fleming
2013-04-09 16:25 ` [PATCH 0/6] Chainsaw efivars.c H. Peter Anvin
2013-04-09 16:50 ` Matt Fleming
2013-04-17 12:47 [PATCH v3 " Matt Fleming
2013-04-17 12:47 ` [PATCH 1/6] efi: move utf16 string functions to efi.h Matt Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1365592717.3072.57.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mikew@google.com \
--cc=teg@jklm.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).