From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38383) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y1ApQ-0006em-Jb for qemu-devel@nongnu.org; Wed, 17 Dec 2014 04:23:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y1ApG-00070H-8I for qemu-devel@nongnu.org; Wed, 17 Dec 2014 04:23:32 -0500 Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:41800) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y1ApG-00070A-1f for qemu-devel@nongnu.org; Wed, 17 Dec 2014 04:23:22 -0500 Received: by mail-wg0-f46.google.com with SMTP id x13so19617932wgg.5 for ; Wed, 17 Dec 2014 01:23:21 -0800 (PST) Sender: Paolo Bonzini Message-ID: <54914B85.7070605@redhat.com> Date: Wed, 17 Dec 2014 10:23:17 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1418399932-7658-1-git-send-email-lersek@redhat.com> <1418399932-7658-2-git-send-email-lersek@redhat.com> <20141216134858.GD3283@hawk.usersys.redhat.com> <5490815E.8@redhat.com> <54908CB6.8030501@redhat.com> <549090D8.5010006@redhat.com> <549098D2.5020001@redhat.com> <54910F67.2000804@redhat.com> In-Reply-To: <54910F67.2000804@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 1/8] fw_cfg: max access size and region size are the same for MMIO data reg List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek , Andrew Jones Cc: peter.maydell@linaro.org, Alexander Graf , qemu-devel@nongnu.org On 17/12/2014 06:06, Laszlo Ersek wrote: >> > That said, the standalone selector is used by BE platforms only, so we >> > know that the standalone selector is always DEVICE_BIG_ENDIAN. > This series exposes the standalone selector (as MMIO) to ARM guests as > well; and in "Documentation/devicetree/bindings/arm/fw-cfg.txt" for the > kernel I'm saying that the selector is little endian. > > Therefore I think that the standalone selector is not only (going to be) > used by BE platforms (or I don't understand your above statement > correctly). It's not going to be used only by BE platforms. But so far it is used by BE platforms only. If you want to keep everything consistent, you can make it (and the wide datum) BE; and swizzle data in the firmware. Otherwise, NATIVE_ENDIAN is fine. > In other words, the standalone selector is NATIVE_ENDIAN, but in the > description of the *ARM* bindings, we can simply say that it's little > endian. Yes. Paolo