Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ctirad Fertr <c.fertr@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] 1616(M) cardbus improvements
Date: Tue, 4 Dec 2007 00:43:25 +0100	[thread overview]
Message-ID: <200712040043.25400.c.fertr@gmail.com> (raw)
In-Reply-To: <s5h8x4cdt31.wl%tiwai@suse.de>

Dne Monday 03 of December 2007 10:29:38 jste napsal(a):

> In my patch, I modified the input put callback to use
> emu1616_src_regs.  Check if it's a wrong implementation.

Oh, you are right. I forgot to add 1616 related code here. Funny I didn't 
noticed any problem in regular use, because I use just analog inputs for 
capture (no difference between 1820 and 1616) and the internal routing worked 
as expected :-)
Thanks for correcting.

> > Unfortunatelly, now I found that driver (or host card) reload causes
> > kernel ooops on 2.6.23 (2.6.22 is unaffected). This is NOT related to my
> > patch.  It crashes even with 1.0.15 version. This is bad :( It crashes
> > immeditely after a firmware for the host card is loaded. Can someone
> > confirm that?
>
> Try HG version whether the same problem occurs.  Many bugs related
> with emu10k1 have been done after 1.0.15.

It seems it was caused by mix of latest driver/headres and older 
alsa-lib/alsa-utils. After upgrade of all components to the latest HG it is 
stable again. The pure 1.0.15 is stable as well with 2.6.13. It was just 
false alarm, fortunatelly.

-----
Ctirad

  reply	other threads:[~2007-12-03 23:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 23:07 [PATCH] 1616(M) cardbus improvements Ctirad Fertr
2007-11-27 16:43 ` Takashi Iwai
2007-11-27 16:45   ` Takashi Iwai
2007-11-27 19:29   ` James Courtier-Dutton
2007-12-02 23:33   ` Ctirad Fertr
2007-12-03  9:29     ` Takashi Iwai
2007-12-03 23:43       ` Ctirad Fertr [this message]
2007-12-13 14:21         ` Takashi Iwai

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=200712040043.25400.c.fertr@gmail.com \
    --to=c.fertr@gmail.com \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox