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: Wed, 07 May 2014 06:32:41 -0700	[thread overview]
Message-ID: <536A35F9.8000904@boundarydevices.com> (raw)
In-Reply-To: <CA+AhUGwq4gXAK7559F1dMPZyQJL=5vJAc7wh-ZdzshzVcdyxbQ@mail.gmail.com>

Hi Erik,

On 05/07/2014 01:02 AM, Erik Botö wrote:
> On Tue, May 6, 2014 at 8:16 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi Erik,
>>
>
> <snip>
>
>>
>> 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.
>
> Thanks for helping out!
>

No problem. That's what we're here for.

> After testing this out and getting really confused about it still not
> working I started to look through the early boot output on the serial
> console looking for some board revision info. Then I noticed that it
> used the sabrelite version of the device tree file since board was
> unset in u-boot. By doing a "setenv board nitrogen6x" in u-boot before
> booting, which makes it use the correct dtb-file, sound works like a
> charm. So I guess it was a user error all along, although a
> not-so-obvious one :)
>
> After upgrading u-boot on the board from "U-Boot
> 2013.01-00058-g5957f6d" to "U-Boot 2014.04" the board variable is set
> by default and hence everything works out-of-the-box.
>

Thanks for the note about this. Since upgrading U-Boot is a
separate operation for our boards, we'll likely have others
hit the same thing as they make the transition to DT.

Regards,


Eric


  reply	other threads:[~2014-05-07 13:32 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
2014-05-07  8:02                   ` Erik Botö
2014-05-07 13:32                     ` Eric Nelson [this message]
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=536A35F9.8000904@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.