All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Pascal Huerst <pascal.huerst@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: sigmadsp: adau1701: Version mismatch while loading firmware in 3.18.3
Date: Wed, 28 Jan 2015 15:00:26 +0100	[thread overview]
Message-ID: <54C8EB7A.7010901@metafoo.de> (raw)
In-Reply-To: <54C8E881.60106@gmail.com>

On 01/28/2015 02:47 PM, Pascal Huerst wrote:
> Hello Lars-Peter,
>
> i followed the instructions on:
>
> http://wiki.analog.com/resources/tools-software/linux-software/sigmadsp_genfirmware
>
> and built the firmware from my xml-file. But when the driver loads, I
> always get:
>
> adau1701 2-0034: Failed to load firmware: Invalid version 2. Supported
> firmware versions: 1
> adau1701 2-0034: Failed to load firmware
> adau1701 2-0034: ASoC: can't set adau1701 hw params: -22
>
> I have been using that .xml/.bin file in 3.14.13 for some time, but now
> in 3.18.3 I always get the version mismatch from above.

Hi,

Are you sure that the you were previously using a v2 firmware file? v2 was 
not supported until recently and loading it with the v1 loader would just 
result in garbage being written to the device.

The patch[1] that adds support for v2 is pretty standalone and you should be 
able to backport it to v3.18.

- Lars

[1] 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/sound/soc/codecs/sigmadsp.c?id=a35daac77a0397d4f23b642d3dc0684682e56cc5

  reply	other threads:[~2015-01-28 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 13:47 sigmadsp: adau1701: Version mismatch while loading firmware in 3.18.3 Pascal Huerst
2015-01-28 14:00 ` Lars-Peter Clausen [this message]
2015-01-28 16:01   ` Pascal Huerst

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=54C8EB7A.7010901@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pascal.huerst@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.