From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Alexander Graf" <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-ppc@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
"Andreas Färber" <afaerber@suse.de>,
"Artyom Tarasenko" <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] m48t59: add mem_base value to m48t59_init_isa()
Date: Mon, 19 Jan 2015 18:17:34 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.11.1501191759410.28301@eddie.linux-mips.org> (raw)
In-Reply-To: <54BD3214.4060209@redhat.com>
On Mon, 19 Jan 2015, Paolo Bonzini wrote:
> >> The reason I asked is simply because ISA devices never do MMIO (apart
> >> for the VGA window).
> >
> > You mean in the QEMU world? At least physical SCSI and Ethernet
> > adapters had a MMIO space for the onboard ROM.
>
> Uh right, ROMs count as MMIO too.
Some ISA Ethernet cards also used MMIO for r/w access, probably to get at
packet memory more efficiently (I don't remember the details offhand) as
port I/O transactions were notoriously slow; in any case this is where the
"Memory" field printed by `ifconfig' under Linux comes from. I'm sure
there was other ISA equipment too using MMIO for one purpose or another.
On a PC/AT class x86 computer these resources would normally be allocated
somehow to the memory space in the 0xd0000-0xeffff range, to work with
real-mode software. With "somehow" usually meaning jumpers, though newer
cards may have had DOS configuration software available to set it up, in a
similar manner to how ECU configured port I/O and MMIO resources for EISA
equipment.
BTW there were ISA DRAM expansion cards in existence too.
Maciej
next prev parent reply other threads:[~2015-01-19 18:17 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
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 [this message]
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=alpine.LFD.2.11.1501191759410.28301@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=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).