From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NVIDIA Tegra DDX
Date: Mon, 10 Dec 2012 09:55:09 -0700 [thread overview]
Message-ID: <50C613ED.4070401@wwwdotorg.org> (raw)
In-Reply-To: <20121210105627.GA7503-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
On 12/10/2012 03:56 AM, Thierry Reding wrote:
...
> Aaron had some reservations about calling this xf86-video-tegra
> because it will clash with the binary tegra_drv.so provided by
> NVIDIA. However I couldn't come up with anything more creative.
> Distributions will have to deal with this in some way or another
> anyway and there really isn't a way of running both drivers on top
> of the same kernel currently, so I decided not to care.
Why not xf86-video-tegradrm, since tegradrm is the kernel driver it
talks to. It'd also help make it more obvious which user-space driver
to pick based on the kernel driver.
prev parent reply other threads:[~2012-12-10 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 10:56 NVIDIA Tegra DDX Thierry Reding
[not found] ` <20121210105627.GA7503-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-12-10 11:01 ` Michal Suchanek
[not found] ` <CAOMqctRAgO-ApTHiPVpcq69e3uE5Ec6N_jxz+wotgvjbhA1tmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-10 11:40 ` Marc Dietrich
2012-12-10 12:34 ` Thierry Reding
[not found] ` <20121210123457.GA22428-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-12-15 13:12 ` Lucas Stach
2012-12-10 16:55 ` Stephen Warren [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=50C613ED.4070401@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org \
--cc=xorg-devel-go0+a7rfsptAfugRpC6u6w@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.