All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: drivers@analog.com, alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 2/8] firmware: Sigma: Skip header during CRC generation
Date: Mon, 28 Nov 2011 08:56:33 +0100	[thread overview]
Message-ID: <4ED33EB1.6030200@metafoo.de> (raw)
In-Reply-To: <201111251500.52711.vapier@gentoo.org>

On 11/25/2011 09:00 PM, Mike Frysinger wrote:
> On Friday 25 November 2011 03:55:42 Lars-Peter Clausen wrote:
>> On 11/24/2011 06:21 PM, Mike Frysinger wrote:
>>> On Thursday 24 November 2011 07:48:21 Lars-Peter Clausen wrote:
>>>> The firmware header is not part of the CRC, so skip it. Otherwise the
>>>> firmware will be rejected due to non-matching CRCs.
>>>
>>> that's because you didn't compare to the right value ;).  include the CRC
>>> -> compare to 0.  omit the CRC -> compare to the CRC value.
>>
>> Does this really work if the CRC is inserted somewhere in the middle of the
>> bytestream?
> 
> i don't think the position matters to the CRC algorithm used by sigmadsp.  
> math principle: a ^ b ^ c is the same thing as b ^ a ^ c and c ^ b ^ a.

If CRC algorithms  were commutative they would be pretty weak, I guess ;)
> 
> i could be wrong as to the CRC algo used though.  simple enough for you to 
> check -- i implemented this firmware code based on a spec i wrote up for the 
> sigmadsp peeps; i never actually had real firmware to test with.
> -mike

It does not work.

- Lars

WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	drivers@analog.com, stable@kernel.org
Subject: Re: [PATCH 2/8] firmware: Sigma: Skip header during CRC generation
Date: Mon, 28 Nov 2011 08:56:33 +0100	[thread overview]
Message-ID: <4ED33EB1.6030200@metafoo.de> (raw)
In-Reply-To: <201111251500.52711.vapier@gentoo.org>

On 11/25/2011 09:00 PM, Mike Frysinger wrote:
> On Friday 25 November 2011 03:55:42 Lars-Peter Clausen wrote:
>> On 11/24/2011 06:21 PM, Mike Frysinger wrote:
>>> On Thursday 24 November 2011 07:48:21 Lars-Peter Clausen wrote:
>>>> The firmware header is not part of the CRC, so skip it. Otherwise the
>>>> firmware will be rejected due to non-matching CRCs.
>>>
>>> that's because you didn't compare to the right value ;).  include the CRC
>>> -> compare to 0.  omit the CRC -> compare to the CRC value.
>>
>> Does this really work if the CRC is inserted somewhere in the middle of the
>> bytestream?
> 
> i don't think the position matters to the CRC algorithm used by sigmadsp.  
> math principle: a ^ b ^ c is the same thing as b ^ a ^ c and c ^ b ^ a.

If CRC algorithms  were commutative they would be pretty weak, I guess ;)
> 
> i could be wrong as to the CRC algo used though.  simple enough for you to 
> check -- i implemented this firmware code based on a spec i wrote up for the 
> sigmadsp peeps; i never actually had real firmware to test with.
> -mike

It does not work.

- Lars

  reply	other threads:[~2011-11-28  7:55 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 12:48 [PATCH 1/8] firmware: Sigma: Prevent out of bounds memory access Lars-Peter Clausen
2011-11-24 12:48 ` Lars-Peter Clausen
2011-11-24 12:48 ` [PATCH 2/8] firmware: Sigma: Skip header during CRC generation Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:21   ` Mike Frysinger
2011-11-25  8:55     ` Lars-Peter Clausen
2011-11-25  8:55       ` Lars-Peter Clausen
2011-11-25 20:00       ` Mike Frysinger
2011-11-25 20:00         ` Mike Frysinger
2011-11-28  7:56         ` Lars-Peter Clausen [this message]
2011-11-28  7:56           ` Lars-Peter Clausen
2011-11-29  5:11           ` Mike Frysinger
2011-11-29  5:11             ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 3/8] firmware: Sigma: Fix endianess issues Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:20   ` Mike Frysinger
2011-11-24 17:20     ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 4/8] firmware: Sigma: Mark firmware strutcs packed Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:19   ` Mike Frysinger
2011-11-25 10:48     ` Lars-Peter Clausen
2011-11-25 20:07       ` Mike Frysinger
2011-11-25 20:07         ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 5/8] ASoC: Move SigmaDSP firmware loader to ASoC Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 13:15   ` [PATCH v2 " Lars-Peter Clausen
2011-11-24 13:15     ` Lars-Peter Clausen
2011-11-24 17:31     ` Mike Frysinger
2011-11-24 17:31       ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 6/8] ASoC: SigmaDSP: Provide diagnostic error messages Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:32   ` Mike Frysinger
2011-11-24 17:32     ` Mike Frysinger
2011-11-25  8:59     ` Lars-Peter Clausen
2011-11-25  8:59       ` Lars-Peter Clausen
2011-11-25 20:02       ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 7/8] ASoC: SigmaDSP: Move private structs and functions to c file Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:31   ` Mike Frysinger
2011-11-24 17:31     ` Mike Frysinger
2011-11-24 12:48 ` [PATCH 8/8] ASoC: SigmaDSP: Add regmap support Lars-Peter Clausen
2011-11-24 12:48   ` Lars-Peter Clausen
2011-11-24 17:30   ` Mike Frysinger
2011-11-25  9:00     ` Lars-Peter Clausen
2011-11-25  9:00       ` Lars-Peter Clausen
2011-11-24 17:26 ` [PATCH 1/8] firmware: Sigma: Prevent out of bounds memory access Mike Frysinger
2011-11-24 17:26   ` Mike Frysinger

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=4ED33EB1.6030200@metafoo.de \
    --to=lars@metafoo.de \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=drivers@analog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=stable@kernel.org \
    --cc=vapier@gentoo.org \
    /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.