qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-ppc@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Alexander Graf" <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa()
Date: Mon, 19 Jan 2015 16:38:29 +0100	[thread overview]
Message-ID: <54BD24F5.70309@suse.de> (raw)
In-Reply-To: <54BD236E.1040200@redhat.com>

Am 19.01.2015 um 16:31 schrieb Paolo Bonzini:
> Is there an "EBus bridge" PCI device similar to the PCI-to-ISA bridge?

In the previous dump, the "ebus" entry looked like one to me?

    bus: pci
      dev: ebus, id ""
        addr = 03.0
        class Bridge, addr 00:03.0, pci id 108e:1000 (sub 1af4:1100)
        bar 0: mem at 0x3000000 [0x3ffffff]
        bar 1: i/o at 0x4000 [0x7fff]
        bus: isa.0
          type ISA

Confusingly named, as "ebus" would be a better type name for the actual
bus, but "EBus" might work as bus name if we actually need one (does the
user add devices to this bus or are these all chipset features
recursively set up by the machine?). Otherwise they could just be
child<> properties on the ebus device.

Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)

  reply	other threads:[~2015-01-19 15:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 11:35 [Qemu-devel] [PATCH 0/2] m48t59: add year offset and MMIO ISA mapping Mark Cave-Ayland
2015-01-19 11:35 ` [Qemu-devel] [PATCH 1/2] m48t59: introduce new year_offset qdev property Mark Cave-Ayland
2015-01-19 12:06   ` Artyom Tarasenko
2015-01-19 12:20     ` Mark Cave-Ayland
2015-01-19 11:35 ` [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa() Mark Cave-Ayland
2015-01-19 12:45   ` Paolo Bonzini
2015-01-19 12:57     ` Artyom Tarasenko
2015-01-19 12:59       ` Paolo Bonzini
2015-01-19 13:12         ` Artyom Tarasenko
2015-01-19 15:01       ` Andreas Färber
2015-01-19 15:22         ` Artyom Tarasenko
2015-01-19 15:31           ` Paolo Bonzini
2015-01-19 15:38             ` Andreas Färber [this message]
2015-01-19 16:01               ` Paolo Bonzini
2015-01-19 16:17             ` Artyom Tarasenko
2015-01-19 16:34               ` Paolo Bonzini
2015-01-19 18:17                 ` Maciej W. Rozycki
2015-01-19 16:57               ` Mark Cave-Ayland
2015-01-19 16:55             ` Mark Cave-Ayland
2015-01-19 20:03           ` Andreas Färber
2015-01-20  9:54             ` Artyom Tarasenko
2015-01-19 16:42         ` Mark Cave-Ayland
2015-01-19 21:16         ` Hervé Poussineau
2015-01-19 15:04       ` Peter Maydell
2015-01-19 16:48         ` Mark Cave-Ayland
2015-01-19 16:50           ` Peter Maydell
2015-01-19 12:09 ` [Qemu-devel] [PATCH 0/2] m48t59: add year offset and MMIO ISA mapping Artyom Tarasenko
2015-01-19 21:59 ` Hervé Poussineau
2015-01-20 10:16   ` Artyom Tarasenko
2015-01-20 14:19   ` Mark Cave-Ayland

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=54BD24F5.70309@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=atar4qemu@gmail.com \
    --cc=hpoussin@reactos.org \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).