All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Giacomo Comes <comes@naic.edu>
Cc: alsa-devel@alsa-project.org, Toyo Abe <toyo.abe@gmail.com>
Subject: Re: Compute Stick baytrail audio problem
Date: Thu, 3 Mar 2016 10:16:25 -0600	[thread overview]
Message-ID: <56D86359.6090800@linux.intel.com> (raw)
In-Reply-To: <20160303040952.GA23703@monopoli.naic.edu>

On 3/2/16 10:09 PM, Giacomo Comes wrote:
> On Wed, Mar 02, 2016 at 11:25:25AM -0600, Pierre-Louis Bossart wrote:
>>
>>>> After some investigation, I found some problems on the driver and fixed a few of
>>>> them. I pushed the fix to my github. I hope it might help you.
>>>>    https://raw.githubusercontent.com/toyoabe/baytrailaudio/fix-underrun/hdmi_audio_20150319.patch
>>>>
>>>> Best Regards,
>>>> -toyo
>>>
>>> Hi,
>>> that was it!. I added your changes and now the audio works. I'm happy.
>>> I got finally every subsystem of the Compute Stick working.
>>
>> If anyone is interested, I ported the code to v4.4, it seems to work
>> on the Baytrail Compute stick w/ Ubuntu.
>>
>> https://github.com/plbossart/sound/commits/baytrail-stick-rebase-4.4
>>
>> Testers welcome, next steps are to add the CherryTrail parts, rebase
>> to the drm-nightly-build branch and start talking upstream changes.
>
> I tested your rebased code and it works for me. Actually I haven't
> used a 4.4 kernel but a 4.1 (openSUSE 42.1). I made a diff between
> kernel 4.4 and your branch and then applied that diff (with very minor changes)
> to the 4.1 openSUSE kernel. No sound issue so far.

Thanks for testing.
There are significant changes needed to apply the initial driver on 3.18 
and 4.0, but the changes are minor after that and largely cosmetic.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 20:39 Compute Stick baytrail audio problem Giacomo Comes
2016-02-20 15:12 ` Pierre-Louis Bossart
2016-02-23  1:15   ` Giacomo Comes
     [not found]   ` <56CBCB86.8040601@gmail.com>
2016-02-23 14:34     ` Giacomo Comes
2016-02-24  9:48       ` Toyo Abe
2016-03-02 17:25       ` Pierre-Louis Bossart
2016-03-03  4:09         ` Giacomo Comes
2016-03-03 16:16           ` Pierre-Louis Bossart [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=56D86359.6090800@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=comes@naic.edu \
    --cc=toyo.abe@gmail.com \
    /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.