From: Scott Wood <scottwood@freescale.com>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"agraf@suse.de" <agraf@suse.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Jia Hongtao-B38951 <B38951@freescale.com>
Subject: Re: [PATCH 0/3] powerpc/fsl: PCI refactoring and QEMU paravirt platform
Date: Fri, 29 Jun 2012 11:59:50 -0500 [thread overview]
Message-ID: <4FEDDF06.10006@freescale.com> (raw)
In-Reply-To: <94F013E7935FF44C83EBE7784D62AD3F09348F0B@039-SN2MPN1-022.039d.mgd.msft.net>
On 06/29/2012 11:18 AM, Li Yang-R58472 wrote:
>
>
>> -----Original Message----- From: Wood Scott-B07421 Sent: Friday,
>> June 29, 2012 11:02 AM To: Kumar Gala Cc: Jia Hongtao-B38951; Wood
>> Scott-B07421; Li Yang-R58472; agraf@suse.de;
>> linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH 0/3] powerpc/fsl:
>> PCI refactoring and QEMU paravirt platform
>>
>> On 06/29/2012 10:57 AM, Kumar Gala wrote:
>>> Pretty sure the boards have ISA, if you see the .dts has
>>> references to
>> 'ISA bridge' & 'i8259' PIC.
>>
>> OK. How about looking for an i8259 node as well?
>
> That could work, but looks hackish. Our proposal for adding a new
> device tree property is a generic solution.
Yes, all *new* boards should have an isa node. But we want to remain
compatible with existing device trees.
> The only problem is that
> new kernels would work with old device trees. I think we can use
> your solution for transitional period. And go for a well defined
> device tree binding for this in long run.
The "transitional period" is until we no longer care about these
specific boards, or any out-of-tree derivatives.
-Scott
next prev parent reply other threads:[~2012-06-29 17:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 23:48 [PATCH 0/3] powerpc/fsl: PCI refactoring and QEMU paravirt platform Scott Wood
2012-06-27 23:50 ` [PATCH 1/3] powerpc/fsl-pci: provide common PCI init Scott Wood
2012-06-27 23:50 ` [PATCH 2/3] powerpc/e500: add paravirt QEMU platform Scott Wood
2012-07-06 12:29 ` Alexander Graf
2012-07-06 16:25 ` Scott Wood
2012-07-06 16:30 ` Alexander Graf
2012-07-06 16:52 ` Scott Wood
2012-07-06 16:59 ` Alexander Graf
2012-07-06 22:04 ` Scott Wood
2012-06-27 23:50 ` [PATCH 3/3] powerpc/mpc85xx_ds: convert to unified PCI init Scott Wood
2012-07-10 18:31 ` Kumar Gala
2012-06-28 4:06 ` [PATCH 0/3] powerpc/fsl: PCI refactoring and QEMU paravirt platform Jia Hongtao-B38951
2012-06-28 16:31 ` Scott Wood
2012-06-29 2:36 ` Jia Hongtao-B38951
2012-06-29 15:57 ` Kumar Gala
2012-06-29 16:01 ` Scott Wood
2012-06-29 16:04 ` Kumar Gala
2012-06-29 16:18 ` Li Yang-R58472
2012-06-29 16:59 ` Scott Wood [this message]
2012-06-29 16:06 ` Zang Roy-R61911
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=4FEDDF06.10006@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B38951@freescale.com \
--cc=agraf@suse.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.com \
/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.