From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT e813376] Sparc32: fix fdc io_base
Date: Sat, 18 Jul 2009 00:37:17 +0100 [thread overview]
Message-ID: <200907180037.17890.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580907171229l7f4b98abtae4a774a252d39f8@mail.gmail.com>
> > The qdev support for this device is almost completely bogus.
> >...
> > The mem_mapped property is also fairly suspect. We almost certainly want
> > two different devices. On SysBus device a MMIO region, and the other an
> > ISA device (using IO ports) - Note that qdev ISA bus support does not
> > exist yet.
>
> How about this cleanup?
It's a start. However the init code is still backwards. For example:
>@@ -1944,6 +1937,7 @@ fdctrl_t *sun4m_fdctrl_init
> fdctrl = FROM_SYSBUS(fdctrl_t, s);
>+ fdctrl->sun4m = 1;
> fdctrl_init_common(fdctrl, -1, io_base, fds);
This code should be in sun4m_fdc_init1.
sun4m_fdctrl_init should really live in sun4m.c, not fdc.c. This should make
it clear whether you're honoring the abstraction boundaries.
>+ .qdev.props = (Property[]) {
> {/* end of properties */}
> }
It is not necessary to specify an empty property list.
Paul
next prev parent reply other threads:[~2009-07-17 23:37 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 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT e813376] Sparc32: fix fdc io_base Anthony Liguori
2009-07-17 14:58 ` Paul Brook
2009-07-17 17:37 ` Blue Swirl
2009-07-17 19:29 ` Blue Swirl
2009-07-17 23:37 ` Paul Brook [this message]
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=200907180037.17890.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.