From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/11] ISA bus improvements
Date: Sun, 18 Sep 2011 21:33:38 +0200 [thread overview]
Message-ID: <4E764792.4030407@reactos.org> (raw)
In-Reply-To: <4E7644CE.9090509@web.de>
Jan Kiszka a écrit :
> On 2011-09-18 16:56, Hervé Poussineau wrote:
>> Following patches aim to change ISA bus to a first-citizen class in Qemu.
>>
>> They add ISA bus ops, like for scsi and usb buses.
>>
>> Current ISA bridges (PIIX3, PIIX4, EBUS and VT82C686) are converted
>> to this new API, and a simple 'isabus-bridge' device is added.
>>
>> isa_address_space() operation can probably be used to remove the
>> infamous isa_mem_base variable. However, some work is already done
>> in this direction on the ML, so I didn't change anything.
>>
>> Finally, add bus argument to isa_create() functions, so architectures
>> with multiple ISA buses (like some Alpha systems) can be emulated.
>>
>> As RFC didn't receive much comments, I put this serie as patches.
>
> Nice work. I had something similar unfinished here, but this one looks
> better on first glace.
Thanks.
>
> Still, I would go one step further and kill the global default isa_bus:
> all ISA API user should pass in the bus they created and obtained from
> some creator.
>
That's indeed the next step I have in mind.
It shouldn't be hard to do; that's mostly adding an isa_bus parameter in
all functions from ISA bridge creation to all ISA devices. However, lots
of prototypes will probably have to be changed, so I wanted to do it in
a second patchset.
Hervé
prev parent reply other threads:[~2011-09-18 19:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 14:56 [Qemu-devel] [PATCH 00/11] ISA bus improvements Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 01/11] isa: rename isa_bus_new to isa_bus_bridge_init Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 02/11] isa: rework ISA bus internals, and add ISA bus ops structure Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 03/11] isa: implement isa_address_space() as a method of ISA bus Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 04/11] audio: give ISA bus to sound cards, instead of PIC Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 05/11] pc: improve bus implementation of PIIX3 bridge Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 06/11] fulong2e: move pic initialization + ISA bus creation to south bridge Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 07/11] sun4u: improve bus implementation of EBus bridge Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 08/11] malta: improve bus implementation of PIIX4 bridge Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 09/11] isa: remove unused parameter to isa_bus_bridge_init() Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 10/11] isa: give bus to isa_create() methods Hervé Poussineau
2011-09-18 14:56 ` [Qemu-devel] [PATCH 11/11] isa: remove limitation of only one ISA bus Hervé Poussineau
2011-09-18 19:21 ` [Qemu-devel] [PATCH 00/11] ISA bus improvements Jan Kiszka
2011-09-18 19:33 ` Hervé Poussineau [this message]
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=4E764792.4030407@reactos.org \
--to=hpoussin@reactos.org \
--cc=jan.kiszka@web.de \
--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).