All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Cédric Le Goater" <clg@kaod.org>,
	qemu-ppc@nongnu.org, "Alexander Graf" <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] ppc/pnv: add a PnvChip object
Date: Tue, 16 Aug 2016 12:18:44 +1000	[thread overview]
Message-ID: <20160816021844.GA14530@voom.fritz.box> (raw)
In-Reply-To: <1470437001.12584.170.camel@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

On Sat, Aug 06, 2016 at 08:43:21AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2016-08-05 at 18:48 +0200, Cédric Le Goater wrote:
> > The core initialization should be ok but building the device 
> > tree might be a bit of a burden if we have to 'cast' in the chip 
> > type we need. We will see.
> 
> We don't cast, we use a method.

Right.  You can have a look at the sPAPR VIO stuff for an example
where we use a method in the individual devices to do the device
specific fdt construction.

> 
> > So what would be the big differences with what we have today ?   
> 
> The XSCOM controller has a different address decoding scheme, so
> we'll have two variants and a base class there. The number and
> location of functional units changes, so we'll probably need to make
> them properties or something, the core XSCOM addressing is completely
> different, we use PHB4 rather than PHB3, etc...
> 
> (Note that for PHB we should probably rename PHB3 to PnvPhb with a
> subclass as well as there is a lot in common between the two, though
> the PBCQ bit is quite different).
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-16  2:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  9:15 [Qemu-devel] [PATCH 0/3] ppc/pnc: add a minimal platform Cédric Le Goater
2016-08-05  9:15 ` [Qemu-devel] [PATCH 1/3] ppc/pnv: add skeleton PowerNV platform Cédric Le Goater
2016-08-16  2:12   ` David Gibson
2016-08-26 14:47     ` Cédric Le Goater
2016-08-26 22:48       ` Benjamin Herrenschmidt
2016-08-29 14:17         ` David Gibson
2016-08-29 14:16       ` David Gibson
2016-08-05  9:15 ` [Qemu-devel] [PATCH 2/3] ppc/pnv: add a PnvChip object Cédric Le Goater
2016-08-05  9:44   ` Benjamin Herrenschmidt
2016-08-05 16:48     ` Cédric Le Goater
2016-08-05 22:43       ` Benjamin Herrenschmidt
2016-08-16  2:18         ` David Gibson [this message]
2016-08-16  2:21   ` David Gibson
2016-08-26 16:31     ` Cédric Le Goater
2016-08-05  9:15 ` [Qemu-devel] [PATCH 3/3] ppc/pnv: add a PowerNVCPUCore object Cédric Le Goater
2016-08-16  2:39   ` David Gibson
2016-08-16  5:02     ` Benjamin Herrenschmidt
2016-08-26 17:55       ` Cédric Le Goater
2016-08-26 17:49     ` Cédric Le Goater
2016-08-29 14:30       ` David Gibson
2016-08-30  6:15         ` Benjamin Herrenschmidt
2016-08-30  6:28           ` David Gibson
2016-08-31  1:06             ` Benjamin Herrenschmidt
2016-08-30  7:23           ` Cédric Le Goater
2016-09-05  1:45             ` David Gibson
2016-09-06  7:45               ` Cédric Le Goater

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=20160816021844.GA14530@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=clg@kaod.org \
    --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.