From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E
Date: Mon, 5 Jan 2009 19:37:08 +0300 [thread overview]
Message-ID: <20090105163708.GB7345@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <950062C1-9944-4B34-9D1D-18F35E1933E2@kernel.crashing.org>
On Thu, Jan 01, 2009 at 08:29:39AM -0600, Kumar Gala wrote:
[...]
>>>>>> + compatible = "fsl,mpc8315-pcie", "fsl,mpc8314-pcie";
>>>>>> + reg = <0xe0009000 0x00001000 0xb0000000 0x01000000>;
>>>>>
>>>>> the size on the 0xb0000000 seems wrong
>>>>
>>>> This is how FSL U-Boots configure the cfg window, and I'm trying to
>>>> retain the compatibility. Anyway, now Linux maps only the first 4kB
>>>> of that area, so we don't actually care about this, but dts is still
>>>> correct for older u-boots. Newer U-Boots might want to correct this
>>>> value if they want to use other cfg window setup...
>>>
>>> I'd rather not pollute the .dts with this
>>
>> So you prefer to change the cfg window size to 0x1000?
>
> I'd prefer to drop it (assuming that is reasonable).
I see. Yes, we can drop it and just read the outwin0 BAR register
to find out the cfg space base address.
> Does the PCI-express OF draft spec cover describing cfg space
>
> http://playground.sun.com/1275/proposals/New/516-it.txt
If I understood correctly, the spec describes directly mapped
cfg space, this won't work for 83xx PCI-E.
I'll post new patches soon.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
prev parent reply other threads:[~2009-01-05 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 16:40 [PATCH 4/4] powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E Anton Vorontsov
2008-12-30 17:46 ` Kumar Gala
2008-12-30 20:19 ` [PATCH v2 " Anton Vorontsov
2008-12-31 16:48 ` Kumar Gala
2008-12-31 17:10 ` Wolfgang Denk
2009-01-01 14:26 ` Kumar Gala
2009-01-05 17:46 ` Scott Wood
2009-01-05 18:01 ` Anton Vorontsov
2009-01-06 12:18 ` Leon Woestenberg
2009-01-07 15:43 ` Scott Wood
2009-01-06 18:53 ` Leon Woestenberg
2009-01-06 19:27 ` Anton Vorontsov
2009-01-06 20:38 ` Kumar Gala
2009-01-06 21:15 ` Anton Vorontsov
2009-01-06 22:33 ` Leon Woestenberg
2009-01-06 23:42 ` Anton Vorontsov
2009-01-07 0:40 ` Leon Woestenberg
2008-12-31 17:41 ` Anton Vorontsov
2009-01-01 14:29 ` Kumar Gala
2009-01-05 16:37 ` Anton Vorontsov [this message]
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=20090105163708.GB7345@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.