From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/7] [POWERPC] mpc8568mds.dts: fix PCI/PCIe nodes
Date: Mon, 8 Oct 2007 12:08:48 +0400 [thread overview]
Message-ID: <20071008120848.3dde6199@kernel.crashing.org> (raw)
In-Reply-To: <EB9BE8E7-6437-403F-A7F4-953B393FDF51@kernel.crashing.org>
Hello Kumar,
On Fri, 5 Oct 2007 15:58:00 -0500
Kumar Gala wrote:
>=20
> On Oct 5, 2007, at 1:05 PM, Anton Vorontsov wrote:
>=20
> > On Fri, Oct 05, 2007 at 09:56:46PM +0400, Sergei Shtylyov wrote:
> >> Hello.
> >>
> >> Anton Vorontsov wrote:
> >>
> >>> Commit 5bece127f0666996ca90772229e00332a34e516c tried to fix
> >>> PCI/PCIe nodes, but actually it broke them even harder. ;-)
> >>
> >> Of course. But shouldn't those be the subnoses of the "soc" =20
> >> type node?
> >
> > Nope. PCI's ranges =3D <>; isn't in the SOC address space.
> >
> > Valentine Barshak posted a patch titled "[RFC] [PATCH] PowerPC: Add =20
> > 64-bit
> > phys addr support to 32-bit pci" that started using =20
> > of_translate_address()
> > for ranges, and of_translate_address() will not work if PCI placed =20
> > in the
> > SOC node. Not sure if that patch applied or not, though.
>=20
> I'm confused, what's the actual issue with PCI that this patch =20
> addresses?
>=20
=46rom what I can see, move of the PCI node out of the SoC node, inspired by =
the recent flame talk about it :)
I guess pretty soon, we'll have "proper" ranges parsing for pci, that does =
of_translate_address() and requires
either tuned-up parent ranges, or residing outside of the SoC node, this is=
the reason...
> - k
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
--=20
Sincerely, Vitaly
next prev parent reply other threads:[~2007-10-08 8:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 17:40 [PATCH respin 0/7] MPC8568E-MDS related patches Anton Vorontsov
2007-10-05 17:46 ` [PATCH 7/7] [POWERPC][SPI] spi_mpc83xx: allow use on any processors with QUICC Engine Anton Vorontsov
2007-10-05 17:46 ` [PATCH 6/7] [POWERPC] mpc8568mds.dts: fix PCI/PCIe nodes Anton Vorontsov
2007-10-05 17:56 ` Sergei Shtylyov
2007-10-05 18:01 ` Scott Wood
2007-10-05 18:05 ` Anton Vorontsov
2007-10-05 20:58 ` Kumar Gala
2007-10-08 8:08 ` Vitaly Bordug [this message]
2007-10-08 12:08 ` Anton Vorontsov
2007-10-08 13:32 ` Kumar Gala
2007-10-08 18:18 ` Kumar Gala
2007-10-05 17:46 ` [PATCH 5/7] [POWERPC] mpc85xx_mds: reset UCC ethernet properly Anton Vorontsov
2007-10-05 17:46 ` [PATCH 4/7] [POWERPC] mpc8568mds: update dts to be able to use UCCs Anton Vorontsov
2007-10-05 17:47 ` [PATCH 3/7] [POWERPC] QE pario: support for MPC85xx layout Anton Vorontsov
2007-10-05 17:47 ` [PATCH 2/7] [POWERPC] QEIC: Implement pluggable handlers, fix MPIC cascading Anton Vorontsov
2007-10-05 17:47 ` [PATCH 1/7] [POWERPC] mpc85xx_mds: select QUICC_ENGINE Anton Vorontsov
2007-10-05 22:09 ` [PATCH respin 0/7] MPC8568E-MDS related patches Kumar Gala
2007-10-08 12:16 ` Anton Vorontsov
2007-10-08 13:46 ` Kumar Gala
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=20071008120848.3dde6199@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).