All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Harry van Haaren <harryhaaren@gmail.com>,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA snd-fireworks Echo AudioFire 2
Date: Mon, 25 Aug 2014 14:52:20 +0200	[thread overview]
Message-ID: <53FB3184.3060201@ladisch.de> (raw)
In-Reply-To: <CAKudYbMC-jioVYJ3ViJWYuWZmPy_vbVXqgHorC7ZQFbBUXCDqQ@mail.gmail.com>

Harry van Haaren wrote:
> [  190.433203] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 0A
> [  190.591959] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02
> [  190.749202] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 12
> [  190.908270] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 12
> [  191.066267] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 0A
> [  191.225139] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02
> [  191.383942] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02
>
> JACK also reports xruns, same as before: flashing the firmware to the
> latest doesn't seem to have changed anything. The firmware of this
> device was at 5.7 before the flash, perhaps its "too new" for
> snd-fireworks in its current state?

I suspect these counter values are generated by the hardware; I don't
think that the firmware can do anything to affect this.
I'll have to check with my own AF2 (which has a much older firmware).


Regards,
Clemens

  reply	other threads:[~2014-08-25 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKudYbO=FZwPHzgxwYADxdUKHOtSUzd5V7WayENkmcz__unFQA@mail.gmail.com>
2014-08-25  4:21 ` ALSA snd-fireworks Echo AudioFire 2 Takashi Sakamoto
2014-08-25 12:09   ` Harry van Haaren
2014-08-25 12:52     ` Clemens Ladisch [this message]
2014-08-25 20:42       ` Clemens Ladisch
2014-08-25 23:10     ` Takashi Sakamoto

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=53FB3184.3060201@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=harryhaaren@gmail.com \
    --cc=o-takashi@sakamocchi.jp \
    /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.