All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] [PATCH 4 of 4] [qemu ppc pci] Emulate
Date: Fri, 28 Mar 2008 15:32:02 +0000	[thread overview]
Message-ID: <1206718322.6320.4.camel@thinkpadL> (raw)


On Fri, 2008-03-28 at 10:10 +0100, Christian Ehrhardt wrote:
> Hollis Blanchard wrote:
> 
> I always used a bamboo.dts -> dtb out of my kernel tree and used that one along time, so I never saw this issue.
> I tried to convert this bamboo.dts file in qemu into a dtb file today and saw that it does not compile (nether with nor without that new patch, the patch only pointed me to that file).
> 
> paelzer@HeliosPrime ~/Desktop/KVM/ppc_port/kvm-userspace-vio/qemu/pc-bios $ dtc -I dts -O dtb -o bamboo.dtb2 bamboo.dts
> DTC: dts->dtb  on file "bamboo.dts"
> bamboo.dts:20 syntax error
> FATAL ERROR: Couldn't read input tree
> 
> Is this correct/expected atm or do we have to fix something here before this goes upstream ?
> 

This must be a dtc versioning issue. My version of dtc compiles the code
fine without issue. But you may have a really older version. Hollis had
spotted a bit of the same problem yesterday.

I am using dtc version:
dtc -v
Version: DTC 1.1.0-g2512a7eb


Are you using an older version then this one. If so time for everyone to
upgrade.


> > diff --git a/qemu/pc-bios/bamboo.dts b/qemu/pc-bios/bamboo.dts
> > --- a/qemu/pc-bios/bamboo.dts
> > +++ b/qemu/pc-bios/bamboo.dts
> > @@ -187,6 +187,45 @@
> > 
> >  		};
> > 
> > +		PCI0: pci@ec000000 {
> > +			device_type = "pci";
> > +			#interrupt-cells = <1>;
> > +			#size-cells = <2>;
> > +			#address-cells = <3>;
> > +			compatible = "ibm,plb440ep-pci", "ibm,plb-pci";
> > +			primary;
> > +			reg = <0 eec00000 8     /* Config space access */
> > +			       0 eed00000 4     /* IACK */
> > +			       0 eed00000 4     /* Special cycle */
> > +			       0 ef400000 40>;  /* Internal registers */
> > +  
> > +			/* Outbound ranges, one memory and one IO,
> > +			 * later cannot be changed. Chip supports a second
> > +			 * IO range but we don't use it for now
> > +			 */
> > +			ranges = <02000000 0 a0000000 0 a0000000 0 20000000
> > +				  01000000 0 00000000 0 e8000000 0 00010000>;
> > +  
> > +			/* Inbound 2GB range starting at 0 */
> > +			dma-ranges = <42000000 0 0 0 0 0 80000000>;
> > +  
> > +			/* Bamboo has all 4 IRQ pins tied together per slot */
> > +			interrupt-map-mask = <f800 0 0 0>;
> > +			interrupt-map = <
> > +				/* IDSEL 1 */
> > +				0800 0 0 0 &UIC0 1c 8
> > +  
> > +				/* IDSEL 2 */
> > +				1000 0 0 0 &UIC0 1b 8
> > +  
> > +				/* IDSEL 3 */
> > +				1800 0 0 0 &UIC0 1a 8
> > +  
> > +				/* IDSEL 4 */
> > +				2000 0 0 0 &UIC0 19 8
> > +			>;
> > +		};
> > +
> >  	};
> > 
> >  	chosen {
> > 
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> > _______________________________________________
> > kvm-ppc-devel mailing list
> > kvm-ppc-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
> 
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

             reply	other threads:[~2008-03-28 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 15:32 Jerone Young [this message]
2008-03-28 15:40 ` [kvm-ppc-devel] [PATCH 4 of 4] [qemu ppc pci] Emulate Jerone Young

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=1206718322.6320.4.camel@thinkpadL \
    --to=jyoung5@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.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.