From: Pascal Huerst <pascal.huerst@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org
Subject: sigmadsp: adau1701: Version mismatch while loading firmware in 3.18.3
Date: Wed, 28 Jan 2015 14:47:45 +0100 [thread overview]
Message-ID: <54C8E881.60106@gmail.com> (raw)
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.
What am I doing wrong?
regards
pascal
next reply other threads:[~2015-01-28 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 13:47 Pascal Huerst [this message]
2015-01-28 14:00 ` sigmadsp: adau1701: Version mismatch while loading firmware in 3.18.3 Lars-Peter Clausen
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=54C8E881.60106@gmail.com \
--to=pascal.huerst@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
/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