From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: Joao Pinto <Joao.Pinto@synopsys.com>,
Liviu Dudau <Liviu.Dudau@arm.com>, <catalin.marinas@arm.com>,
<linux-pci@vger.kernel.org>
Subject: Re: Request for Info: Designware PCIe Root Complex support in ARM64
Date: Tue, 15 Mar 2016 11:33:28 +0000 [thread overview]
Message-ID: <56E7F308.2020907@synopsys.com> (raw)
In-Reply-To: <20160314121538.GB6629@red-moon>
Hi!
Just built the linux-next for ARM64 and built beautifully so there is no issue.
I was having an issue using 3.18, but with this new kernel no issues were found.
Thanks for all your inputs!
Joao
On 3/14/2016 12:15 PM, Lorenzo Pieralisi wrote:
> On Fri, Mar 11, 2016 at 01:46:00PM -0600, Bjorn Helgaas wrote:
>> [+cc Lorenzo]
>>
>> On Fri, Mar 11, 2016 at 11:33:12AM +0000, Joao Pinto wrote:
>>> Hi Liviu, Catalin and Bjorn,
>>>
>>> I am currently working on the PCIe Root Complex based on the Designware Core
>>> (/pci/host/pcie-desigware.c). I have noticed that currently building a solution
>>> based on the previous for an ARM64 CPU is problematic and demands some tweaking
>>> in the ARM64 arch (like adding some functions in the pcibios, etc.).
>>
>> If I understand you correctly, you're saying that pcie-designware.c
>> doesn't build on arm64. It would be helpful to know exactly what
>> problem you're seeing (what kernel version, what config, what the
>> error are, etc.)
>
> Yes, I am not sure I understand what Joao is referring to so I would
> be grateful if he can provide us with additional details.
>
> Thanks,
> Lorenzo
>
prev parent reply other threads:[~2016-03-15 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 11:33 Request for Info: Designware PCIe Root Complex support in ARM64 Joao Pinto
2016-03-11 11:49 ` Liviu Dudau
2016-03-11 19:46 ` Bjorn Helgaas
2016-03-14 12:15 ` Lorenzo Pieralisi
2016-03-15 11:33 ` Joao Pinto [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=56E7F308.2020907@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=Liviu.Dudau@arm.com \
--cc=catalin.marinas@arm.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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 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).