From: andrzej zaborowski <balrogg@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix console_write_ch on 64-bit big-endian hosts
Date: Wed, 2 Jun 2010 21:31:47 +0200 [thread overview]
Message-ID: <AANLkTineMzEVSmN7OCuDwkTg_tMdcDNfmCWyV2BwLgNs@mail.gmail.com> (raw)
In-Reply-To: <1275505133-3734-1-git-send-email-aliguori@us.ibm.com>
Hi,
On 2 June 2010 20:58, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Currently, console_ch_t is defined as an unsigned long. However, immediately
> after it's definition, we treat it as a uint32_t *. This will work on a little
> endian system because of the way bits are layed out but will fail miserably
> on big endian hosts.
It seems that what this really tries to do is like *dest =
leul_to_cpu(v) from bswap.h? (Or cpu_to_leul.. quite difficult to wrap
my head around it..)
Cheers
next prev parent reply other threads:[~2010-06-02 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 18:58 [Qemu-devel] [PATCH] Fix console_write_ch on 64-bit big-endian hosts Anthony Liguori
2010-06-02 19:31 ` andrzej zaborowski [this message]
2010-06-02 20:32 ` Anthony Liguori
2010-06-02 20:58 ` andrzej zaborowski
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=AANLkTineMzEVSmN7OCuDwkTg_tMdcDNfmCWyV2BwLgNs@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).