From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dylan Reid <dgreid-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Re: HDMi out on Venice2
Date: Mon, 5 May 2014 22:32:49 +0200 [thread overview]
Message-ID: <20140505203248.GA27821@mithrandir> (raw)
In-Reply-To: <CAEUnVG6TcgJ+TB6r11Rsp=LNCvuRawLNXNdfCspF0JpHx1=M4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Mon, May 05, 2014 at 12:07:51PM -0700, Dylan Reid wrote:
> Hi Thierry,
>
> Did you have to make any user-space changes to test the HDMI output on
> Venice2? I've got your recent patch series and see the hdmi device
> being probed but I haven't figured out how to get X to use it. I'm
> using the sample rootfs that was posted for the Jetson board.
I've used custom userspace, but I would expect regular X to work with
the patches as well. The sample rootfs probably comes with only the
NVIDIA Tegra X driver installed. Have you tried installing the
xf86-video-modesetting driver? That should automatically use the HDMI
output if it's connected to a monitor. If not you should still be able
to manually configure the outputs using xrandr.
> My goal is to be able to test the hdmi audio changes on this as well
> as our downstream kernel.
Note that while there's some code to support HDMI audio, nobody's ever
tested this upstream and it's likely not to work. So I think there may
be more work required to get that running. I can help out with that,
it's been on my list of things to do for a while.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-05 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 19:07 HDMi out on Venice2 Dylan Reid
[not found] ` <CAEUnVG6TcgJ+TB6r11Rsp=LNCvuRawLNXNdfCspF0JpHx1=M4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-05 20:32 ` Thierry Reding [this message]
2014-05-06 2:14 ` Dylan Reid
2014-05-05 21:16 ` Stephen Warren
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 1:23 Dylan Reid
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=20140505203248.GA27821@mithrandir \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dgreid-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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;
as well as URLs for NNTP newsgroup(s).