From: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
To: Richard Leitner <me-M/VWbR8SM2SsTnJN9+BGXg@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Question about "missing" tegra features
Date: Thu, 03 Jul 2014 09:41:16 +0200 [thread overview]
Message-ID: <1438574.hj9VjvJZ8S@fb07-iapwap2> (raw)
In-Reply-To: <c3a33a3d722302b1f4d877649d485d2f-n3SY6/QrmYUdxdNa7N5bz2CGZHFJa5fA29i0knmqyyNx9qoA87EPLA@public.gmane.org>
Hi Richard,
Am Donnerstag, 3. Juli 2014, 09:11:39 schrieben Sie:
> Hello folks,
> I've a general question regarding the linux-tegra development:
> Why are there tegra features which are available in NVIDIA's kernel tree
> [1], but not included in mainline (or at least your tegra tree)?
> I've just noticed that for the USB device controller
> (drivers/usb/gadget/tegra_udc.{c,h}), but it seems there are more such
> "cases".
without being a NV fellow, I guess it's just a lag of developer resources. My
feeling is that NV releases new SoC versions faster than they can add mainline
support for it, especially for hw blocks which are seldom used.
On the other hand, you are free to forward port drivers you miss and submit
them here. But still then someone has to maintain them.
> Is there any documentation on what is supported/included in mainline
> already and what not?
Maybe it's time to add this information to some wiki, e.g.
http://elinux.org/Tegra
Marc
next prev parent reply other threads:[~2014-07-03 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 7:11 Question about "missing" tegra features Richard Leitner
[not found] ` <c3a33a3d722302b1f4d877649d485d2f-n3SY6/QrmYUdxdNa7N5bz2CGZHFJa5fA29i0knmqyyNx9qoA87EPLA@public.gmane.org>
2014-07-03 7:41 ` Marc Dietrich [this message]
2014-07-21 15:18 ` Stephen Warren
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=1438574.hj9VjvJZ8S@fb07-iapwap2 \
--to=marvin24-mmb7mzphnfy@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=me-M/VWbR8SM2SsTnJN9+BGXg@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