All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "Erik Botö" <erik.boto@pelagicore.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Troy Kisky <troy.kisky@boundarydevices.com>
Subject: Re: No sound on nitrogen6x + linux-boundary 3.10.17
Date: Tue, 06 May 2014 11:16:39 -0700	[thread overview]
Message-ID: <53692707.306@boundarydevices.com> (raw)
In-Reply-To: <CA+AhUGx1gG98v7F7QjwH+H4xZ5kL8WikK7f=TqtEXxjnyWcsWg@mail.gmail.com>

Hi Erik,

On 05/06/2014 07:39 AM, Erik Botö wrote:
> Hi,
>
> On Tue, May 6, 2014 at 4:04 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>
 > <snip>
 >
>>
>> Erik, I'll forward a patch against linux-boundary_3.10.17.bb later
>> today, but you can test by changing SRCREV to
>>          fe41f1e14c1769c2012b21ac6375ddb1ab15ea52
>
> I tried that now but I still can't play anything using alsa (or
> anything else I've tried). Note that this is not just after reboot, I
> also don't have working audio after a cold boot. Looking at the kernel
> output from boot it looks like the driver load just fine, and I have
> the device under /dev/snd/pcmC0D0p and it's listed using aplay -L:
>
> Has anyone been able to test using a sabrelite or nitrogen6x to see if
> they get the same result? I just use aplay to play a test file from
> alsa (/usr/share/sounds/alsa/Front_Left.wav on most linux systems).
>

I just tested against this image, revision fe41f1e of our kernel
and nitrogen6x_defconfig on a Nitrogen6x and things worked
perfectly through a handful of re-boots:

	http://boundarydevices.com/yocto-kernel-3-10-17-beta/

Let me know if you'd like me to upload a binary kernel package.

Regards,


Eric


  reply	other threads:[~2014-05-06 18:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05  6:51 No sound on nitrogen6x + linux-boundary 3.10.17 Erik Botö
2014-05-05 13:24 ` Erik Botö
2014-05-05 14:31   ` Otavio Salvador
2014-05-05 14:32   ` Erik Botö
2014-05-05 17:40 ` Fabio Estevam
2014-05-05 17:55   ` Fabio Estevam
2014-05-05 18:02     ` John Weber
2014-05-05 19:31       ` Eric Nelson
2014-05-05 23:22         ` Troy Kisky
2014-05-05 23:27           ` Fabio Estevam
2014-05-05 23:59             ` Troy Kisky
2014-05-06 14:04             ` Eric Nelson
2014-05-06 14:39               ` Erik Botö
2014-05-06 18:16                 ` Eric Nelson [this message]
2014-05-07  8:02                   ` Erik Botö
2014-05-07 13:32                     ` Eric Nelson
2014-05-28 17:26       ` Fabio Estevam
2014-05-28 19:12         ` John Weber
2014-05-06 12:36     ` Erik Botö

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=53692707.306@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=erik.boto@pelagicore.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=troy.kisky@boundarydevices.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.