From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc <qemu-ppc@nongnu.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-devel] [PATCH] PPC: fix PCI configuration space MemoryRegions for grackle/uninorth
Date: Thu, 19 Dec 2013 08:04:16 +1100 [thread overview]
Message-ID: <1387400656.15680.13.camel@pasglop> (raw)
In-Reply-To: <1E2ED24F-E936-4195-9B3A-C119A9C0582C@suse.de>
On Wed, 2013-12-18 at 13:34 +0100, Alexander Graf wrote:
> Hrm. Are you 100% sure this correct? This UniNorth is a real headache.
> The closest thing to a spec for it is the U4 spec which is generations
> ahead:
>
> http://www.datasheetarchive.com/dl/Datasheets-SW3/DSASW0048084.pdf
>
> On that at page 109 you can see that you do indeed have a range of
> registers and a few fancy modes that can even be used to directly
> access config space registers without the usual index/data cycle.
>
> Ben, do you have any more insight into how the original Uninorth
> worked?
Just index/data. Look at Linux :-)
Cheers,
Ben.
next prev parent reply other threads:[~2013-12-18 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 10:53 [Qemu-devel] [PATCH] PPC: fix PCI configuration space MemoryRegions for grackle/uninorth Mark Cave-Ayland
2013-10-11 18:43 ` Hervé Poussineau
2013-11-08 3:20 ` Alexander Graf
2013-11-08 22:18 ` Mark Cave-Ayland
2013-12-18 12:34 ` Alexander Graf
2013-12-18 21:04 ` Benjamin Herrenschmidt [this message]
2013-12-18 21:24 ` Alexander Graf
2013-12-18 22:04 ` Benjamin Herrenschmidt
2013-12-18 22:07 ` Alexander Graf
2013-12-18 22:10 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-12-19 3:49 ` [Qemu-devel] " Benjamin Herrenschmidt
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=1387400656.15680.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=hpoussin@reactos.org \
--cc=mark.cave-ayland@ilande.co.uk \
--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 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.