All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jack Mitchell <ml-psbXN780rFT10XsdtD+oqA@public.gmane.org>
Cc: Alex Courbot <gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: TX1 mainline GPU/wifi support
Date: Wed, 3 Aug 2016 18:05:26 +0200	[thread overview]
Message-ID: <20160803160526.GA22119@ulmo.ba.sec> (raw)
In-Reply-To: <5654a683-b801-86d5-6699-d41b444c3688-psbXN780rFT10XsdtD+oqA@public.gmane.org>

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

Closing the loop with what was discussed on IRC...

On Tue, Aug 02, 2016 at 01:32:31PM +0100, Jack Mitchell wrote:
> Hi,
> 
> I am currently investigating the opportunity to move our TX1 boards over to
> mainline linux as we require some recent kernel features. I have
> successfully booted linux-next and have USB/ethernet working along with
> Docker and a recent systemd. I see that GPU support is somewhat implemented
> but I'm not sure how to integrate the current nvidia userspace with the
> driver. We use CUDA on our boards, and as such I assume we need the nvidia
> kernel blob to be driving the GPU, right?

That's correct. The Nouveau userspace (and kernel driver for that
matter) don't support CUDA at this point in time. I think some work had
been done on that as part of the A44 project, but I don't know exactly
what the status is.

Alex, do you happen to know?

In order to run the proprietary userspace you'd need a copy of the nvgpu
driver (and possibly other dependencies) from downstream. Porting that
to an upstream kernel is, as far as I understand, non-trivial. So the
bottom line is that you're between a rock and a hard place.

Perhaps one alternative is to connect a discrete GPU via PCIe and use
the proprietary driver for 32-bit ARM. I think people have had some
success using that. That's of course not a very nice solution since it
doesn't make use of the Tegra GPU and requires a lot of extra power.

> As a second question, is there any roadmap for the wifi support on the TX1
> devkit?

I have not looked at wifi at all. I think it's connected via SDIO, so it
might be possible to get it to work with very little effort.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-08-03 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 12:32 TX1 mainline GPU/wifi support Jack Mitchell
     [not found] ` <5654a683-b801-86d5-6699-d41b444c3688-psbXN780rFT10XsdtD+oqA@public.gmane.org>
2016-08-03 16:05   ` 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=20160803160526.GA22119@ulmo.ba.sec \
    --to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ml-psbXN780rFT10XsdtD+oqA@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 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.