qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT e813376] Sparc32: fix fdc io_base
Date: Sat, 18 Jul 2009 11:25:38 +0300	[thread overview]
Message-ID: <f43fc5580907180125v73458380t16d083d64cc592c9@mail.gmail.com> (raw)
In-Reply-To: <200907180037.17890.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

On Sat, Jul 18, 2009 at 2:37 AM, Paul Brook<paul@codesourcery.com> wrote:
>> > 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.

OK. Better now?

> sun4m_fdctrl_init should really live in sun4m.c, not fdc.c. This should make
> it clear whether you're honoring the abstraction boundaries.

I know, but I tried to preserve the existing interface at this stage
of conversion. Later I'm going to move all such init functions to
sun4m.c. Then I should add a SBus bus type.

[-- Attachment #2: 0001-Clean-up-fdc-qdev-conversion.patch --]
[-- Type: application/x-patch, Size: 7503 bytes --]

  reply	other threads:[~2009-07-18  8:26 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
2009-07-18  8:25         ` Blue Swirl [this message]
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=f43fc5580907180125v73458380t16d083d64cc592c9@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=paul@codesourcery.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).