public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: PCIe MSI support
Date: Sat, 3 Dec 2011 12:55:08 +0100	[thread overview]
Message-ID: <20111203115507.GA2887@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <CAOesGMgoYKnv+ATSx9dnShqXJyjW1X1MoVB=bydBoCcH-rDb2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

* Olof Johansson wrote:
> Hi,
> 
> On Thu, Dec 1, 2011 at 11:43 PM, Thierry Reding
> <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org> wrote:
[...]
> > I've verified with a hardware engineer that the voltages indeed seem correct.
> > Even the PCIe reference clock can be measured at the mini-PCIe connectors. So
> > something must be going right.
> 
> Ok, that's interesting. I haven't had a chance to give my harmony a
> spin with a pci-e card here lately, I'll try to give it a go as soon
> as I can but it'll be a few more days.

That'd be great. Perhaps it works fine for you and I'm just doing something
wrong.

[...]
> > I'm thinking about ordering a Trimslice to use for comparison. Has anyone
> > else verified that mainline has working PCIe for Trimslice? I think Mike
> > Rapoport is no longer a regular on this list. His last commits seem to
> > indicate that PCIe was working on Harmony as well at the time, so I'm a
> > little confused about what might have happened since then.
> 
> PCI-e works on mainline on trimslice, I have verified that myself. It
> has ethernet on pci-e, and both u-boot and the kernel can use it.

I've ordered a Trim-Slice and should have it late next week or beginning of
the week after. I can also try an older version of mainline from around the
time that Mike mainlined the Harmony support. I assume that at the time it
must have worked. Perhaps the issue can be bisected.

Unfortunately I'm rather busy with other things as well, so I won't be able
to work on this fulltime.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2011-12-03 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 19:57 PCIe MSI support Thierry Reding
     [not found] ` <20111124195704.GA15417-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2011-11-24 22:42   ` Olof Johansson
     [not found]     ` <CAOesGMjDFsAvvUg8tMt+MbwODVoz3SmW0gqcRsCdD_Zhcz5p4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-02  7:43       ` Thierry Reding
     [not found]         ` <20111202074342.GB10768-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2011-12-02 18:55           ` Olof Johansson
     [not found]             ` <CAOesGMgoYKnv+ATSx9dnShqXJyjW1X1MoVB=bydBoCcH-rDb2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-03 11:55               ` Thierry Reding [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=20111203115507.GA2887@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding-rm9k5ik7kjkj5m59nbduvrnah6klmebb@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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