From: Tyler Yeomans <tyeo098@gmail.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Antonio Ospite <ao2@ao2.it>, Nicolas George <george@nsup.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"Nikula, Jarkko" <jarkko.nikula@intel.com>
Subject: Re: Intel Baytrail Linux Audio
Date: Thu, 23 Jul 2015 11:24:55 -0400 [thread overview]
Message-ID: <55B10747.5000101@gmail.com> (raw)
In-Reply-To: <20150714084755.GA5086@localhost>
Hello Vinod,
Sorry to bother again, is there any update or anything else I can try here?
Thanks,
Tyler
On 07/14/2015 04:47 AM, Vinod Koul wrote:
> On Mon, Jul 13, 2015 at 01:06:47PM -0400, Tyler Yeomans wrote:
>> Vinod,
>>
>> Have you received my last message?
>> The device was originally installed with 8.1, but I have since
>> erased it in favor of Ubuntu.
>>
>> Is there anything I can be trying in the meantime?
>>
>> Thanks-
>>
>> Tyler
>>
>> On 07/10/2015 12:06 AM, Vinod Koul wrote:
>>> On Thu, Jul 09, 2015 at 02:57:58PM -0400, Tyler Yeomans wrote:
>>>> Antonio/Vinod,
>>>>
>>>> I have made the change in the sst-acpi.c file for the atom specific boards.
>>>> I've attached the dmesg output here with dynamic debug enabled.
>>>>
>>>> To clarify-
>>>>
>>>> snd-intel-sst-core is loaded
>>>> FE-BE fix has been applied
>>>> I'm using the ssp0 firmware.
>>>>
>>>> Interrupts are still 0
>>>>
>>>> Still no sound.
> Thanks,
>
> I think the interrupt routing is not right, so am trying ti get answers for
> this, stay tuned :)
>
next prev parent reply other threads:[~2015-07-23 15:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:10 Intel Baytrail Linux Audio Koul, Vinod
2015-07-03 12:36 ` Antonio Ospite
2015-07-03 13:06 ` Nicolas George
[not found] ` <559A90CE.2030105@gmail.com>
[not found] ` <20150707031950.GD11002@localhost>
2015-07-07 14:00 ` Tyler Yeomans
2015-07-07 17:08 ` Vinod Koul
2015-07-07 21:06 ` Tyler Yeomans
2015-07-08 3:36 ` Vinod Koul
2015-07-08 8:23 ` Antonio Ospite
2015-07-08 14:30 ` Tyler Yeomans
2015-07-08 16:21 ` Antonio Ospite
2015-07-08 16:32 ` Tyler Yeomans
2015-07-08 20:17 ` Antonio Ospite
2015-07-08 20:24 ` tyeo098
[not found] ` <559EC436.30900@gmail.com>
2015-07-10 4:06 ` Vinod Koul
2015-07-10 12:41 ` Tyler Yeomans
2015-07-13 17:06 ` Tyler Yeomans
2015-07-14 8:47 ` Vinod Koul
2015-07-23 15:24 ` Tyler Yeomans [this message]
2015-07-10 4:03 ` Vinod Koul
2015-07-08 20:57 ` Luka Karinja
[not found] ` <559D88C1.3010504@bazdara.com>
2015-07-10 4:00 ` Vinod Koul
2015-07-10 15:24 ` Luka Karinja
-- strict thread matches above, loose matches on Subject: below --
2015-07-03 13:43 Koul, Vinod
[not found] <5589D025.7090700@gmail.com>
2015-06-24 10:11 ` Vinod Koul
2015-06-24 14:24 ` Tyler Yeomans
2015-06-24 16:03 ` Vinod Koul
2015-06-24 17:40 ` Tyler Yeomans
2015-06-25 6:38 ` Jarkko Nikula
2015-06-30 18:24 ` Tyler Yeomans
2015-06-30 22:57 ` Tyler Yeomans
2015-07-02 18:40 ` Nicolas George
2015-07-03 8:51 ` Liam Girdwood
2015-07-03 9:08 ` Antonio Ospite
2015-07-03 9:46 ` Nicolas George
2015-07-03 10:32 ` Antonio Ospite
2015-07-03 11:12 ` Nicolas George
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=55B10747.5000101@gmail.com \
--to=tyeo098@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ao2@ao2.it \
--cc=george@nsup.org \
--cc=jarkko.nikula@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox