From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] PCIe support for Tegra T30 ?
Date: Fri, 05 Jul 2013 11:19:04 -0600 [thread overview]
Message-ID: <51D70008.2040405@wwwdotorg.org> (raw)
In-Reply-To: <1373035293.19624.39.camel@lucretius>
On 07/05/2013 08:41 AM, Bob Koninckx wrote:
> Hi,
>
> Are there any plans for adding PCIe support for Tegra T30 SoC in the
> near future? If not, what would it take if we would want to do this
> ourselves. Any pointer in the right directions would be greatly
> appreciated.
I don't believe anyone is actively working on this at present. It would
be great to have this support in place.
If you want to take a crack at it yourself, I suggest the following
resources:
Thierry Reding has recently created a new PCIe driver for Tegra in the
Linux kernel. You can find this as part of:
git://gitorious.org/thierryreding/linux.git next
The downstream U-Boot port for the Tegra20 TrimSlice board has PCIe
support, for the built-in NIC. You can find that at:
git://gitorious.org/trimslice-u-boot/trimslice-u-boot.git master
next prev parent reply other threads:[~2013-07-05 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 14:41 [U-Boot] PCIe support for Tegra T30 ? Bob Koninckx
2013-07-05 17:19 ` Stephen Warren [this message]
2013-07-17 5:35 ` Thierry Reding
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=51D70008.2040405@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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