From: Bob Breuer <breuerr@mc.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] sparc32_dma: separate ledma and espdma
Date: Fri, 17 Dec 2010 14:36:11 -0600 [thread overview]
Message-ID: <4D0BC9BB.9070100@mc.net> (raw)
In-Reply-To: <AANLkTim+QOaRxb41s0nOgGOcsNtTm6kCYq6Whu5suVV5@mail.gmail.com>
Blue Swirl wrote:
> ESP and Lance DMA controllers are not identical.
>
> Separate the controllers on VMState and instantiation level.
>
> NB: This change breaks savevm and migration compatibility.
>
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> ---
> Perhaps the compat properties could be used to retain compatibility.
> But if nobody cares (as I suspect), let's just break it.
>
> Further changes can either use s->is_ledma or make the state
> structures separate.
>
> hw/sparc32_dma.c | 65 ++++++++++++++++++++++++++++++++++++++++++++---------
> hw/sun4m.c | 16 ++++++------
> 2 files changed, 62 insertions(+), 19 deletions(-)
>
This change never made it in, and I found a case that may benefit from it.
The ledma seems to have an extra register that Solaris 9 reads, address
0x78400020 on SS-5, and the OBP properties of a SS-20 do indicate that
there could be up to 32 bytes of registers:
ok cd /iommu/sbus/ledma
ok .attributes
burst-sizes 0000003f
reg 0000000f 00400010 00000020
name ledma
As a hack, you can get Solaris 9 to boot single user by adding this one
line to sun4m_hw_init() in sun4m.c:
empty_slot_init(hwdef->dma_base + 32ULL, 16);
Bob
next prev parent reply other threads:[~2010-12-17 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 11:11 [Qemu-devel] [PATCH] sparc32_dma: separate ledma and espdma Blue Swirl
2010-12-17 20:36 ` Bob Breuer [this message]
2010-12-17 20:56 ` 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=4D0BC9BB.9070100@mc.net \
--to=breuerr@mc.net \
--cc=atar4qemu@gmail.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.