From: David Henningsson <david.henningsson@canonical.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Out-of-tree HDMI audio driver for BayTrail-T
Date: Thu, 27 Aug 2015 08:02:00 +0200 [thread overview]
Message-ID: <55DEA7D8.5060106@canonical.com> (raw)
I don't usually deal with out-of-tree drivers, but when Canonical
enabled the Intel Compute Stick [1] (which is using a BayTrail-T
processor), we were using an out-of-tree driver to enable HDMI audio.
The driver has earlier been made public by Intel [2], and I've put my
modifications to it here [3].
Unfortunately, it looks like the effort and hardware knowledge required
to make this driver upstreamable is beyond what I can currently manage.
Also, I cannot answer for whether or not other parties (such as Intel)
plan to upstream the driver.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
[1]
http://www.intel.com/content/www/us/en/compute-stick/intel-compute-stick.html
[2] https://github.com/01org/baytrailaudio
[3]
http://kernel.ubuntu.com/git/diwic/baytrail-hdmi-audio.git/log/?h=baytrail-T-hdmi-audio
next reply other threads:[~2015-08-27 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 6:02 David Henningsson [this message]
2015-08-27 13:31 ` Out-of-tree HDMI audio driver for BayTrail-T Vinod Koul
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=55DEA7D8.5060106@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.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