alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Sync with AudioScience current CVS at version 4.03.04
Date: Wed, 03 Feb 2010 09:45:26 +1300	[thread overview]
Message-ID: <4B688EE6.8060209@audioscience.com> (raw)
In-Reply-To: <s5h1vh3ad75.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Tue, 02 Feb 2010 21:16:11 +1300,
> Eliot Blennerhassett wrote:
>> Greetings,
>>
>> The just submitted patch requires matching firmware
>> http://audioscience.com/internet/download/firmware/dspbins40304.zip
>>
>> As usual, my apologies for the large patch.  Unfortunately it was not
>> possible to split into unrelated subpatches without manually recreating
>> the commit history from our CVS repository.
> 
> Thanks for the patch.  I applied now together with the firmware update.

Thank you.

> I suppose the new firmware is still compatible with the older one?
> I'm asking this because the files are overridden.

In this case, the firmware and driver are a pair that must go together.
I.e. both the driver and the firmware must be updated together.

If the versions do not match, a warning will be logged.

However, now you mention it, I will look at making it a failure if the
major version of driver vs fimware does not match (we changed from 3. to
4. because the message format is incompatible).
I'll follow up with another patch in the next few days.

regards

Eliot

      reply	other threads:[~2010-02-02 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  8:16 [PATCH] Sync with AudioScience current CVS at version 4.03.04 Eliot Blennerhassett
2010-02-02 15:07 ` Takashi Iwai
2010-02-02 20:45   ` Eliot Blennerhassett [this message]

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=4B688EE6.8060209@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).