From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT e813376] Sparc32: fix fdc io_base
Date: Fri, 17 Jul 2009 09:24:30 -0500 [thread overview]
Message-ID: <4A60899E.6020108@codemonkey.ws> (raw)
In-Reply-To: <200907171104.n6HB4EDY011438@d01av04.pok.ibm.com>
Anthony Liguori wrote:
> From: Blue Swirl <blauwirbel@gmail.com>
>
> On some Sparc32 machines, fdc is located above 4G limit, so uint32_t is not
> appropriate type for io_base.
>
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>
> diff --git a/hw/fdc.c b/hw/fdc.c
> index fa154a3..4ad5e5e 100644
> --- a/hw/fdc.c
> +++ b/hw/fdc.c
> @@ -33,6 +33,7 @@
> #include "qemu-timer.h"
> #include "isa.h"
> #include "sysbus.h"
> +#include "qdev-addr.h"
>
> /********************************************************/
> /* debug Floppy devices */
> @@ -1972,7 +1973,7 @@ static SysBusDeviceInfo fdc_info = {
> .qdev.props = (Property[]) {
> {
> .name = "io_base",
> - .info = &qdev_prop_uint32,
> + .info = &qdev_prop_taddr,
>
fdc probably shouldn't use target_phys_addr_t and instead should just
use a uint64_t for io_base. target_phys is a CPU type, devices
shouldn't depend on it.
What do you think?
Regards,
Anthony Liguori
next parent reply other threads:[~2009-07-17 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907171104.n6HB4EDY011438@d01av04.pok.ibm.com>
2009-07-17 14:24 ` Anthony Liguori [this message]
2009-07-17 14:58 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT e813376] Sparc32: fix fdc io_base Paul Brook
2009-07-17 17:37 ` Blue Swirl
2009-07-17 19:29 ` Blue Swirl
2009-07-17 23:37 ` Paul Brook
2009-07-18 8:25 ` Blue Swirl
2009-07-17 17:28 ` Blue Swirl
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=4A60899E.6020108@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.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).