mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: "The Linux Audio Developers' Mailing List" 
	<linux-audio-dev@music.columbia.edu>
Cc: Raymond Lai <raymond.kk.lai@gmail.com>,
	linux-pcmcia@lists.infradead.org,
	alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-audio-dev] Re: any update on the pcmcia bug blocking Audigy2 notebook sound card driver development
Date: 08 Aug 2005 09:40:24 -0700	[thread overview]
Message-ID: <1123519224.16205.5.camel@cmn37.stanford.edu> (raw)
In-Reply-To: <20050807104332.320aec48.akpm@osdl.org>

On Sun, 2005-08-07 at 10:43, Andrew Morton wrote:
> Raymond Lai <raymond.kk.lai@gmail.com> wrote:
> > Hi all,
> > 
> > I remember there's a kernel pcmcia bug preventing the development for 
> > the Audigy2 pcmcia notebook sound card driver. 
> > 
> > See http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Creative_Labs#matrix
> > 
> > Is there any new updates on the situation? Has the bug been fixed? or
> > anyone working on it?
>
> Is it related to http://bugzilla.kernel.org/show_bug.cgi?id=4788 ?

I think not, the card in question is the Creative Audigy 2 ZS PCMCIA
card. I have one I can't use yet :-( The kernel locks hard when ALSA
tries to load the driver. 

This is the last I heard about this issue:
  http://www.uwsg.iu.edu/hypermail/linux/kernel/0507.1/0978.html

-- Fernando



  parent reply	other threads:[~2005-08-08 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 15:44 Raymond Lai
2005-08-07 17:43 ` Andrew Morton
2005-08-07 18:41   ` [Alsa-devel] " Lee Revell
2005-08-07 20:58     ` Raymond Lai
2005-08-08 16:40   ` Fernando Lopez-Lezcano [this message]
2005-08-09  6:54     ` [Alsa-devel] Re: [linux-audio-dev] " Lee Revell
2005-08-10  9:44       ` Takashi Iwai
2005-08-13 15:08         ` James Courtier-Dutton

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=1123519224.16205.5.camel@cmn37.stanford.edu \
    --to=nando@ccrma.stanford.edu \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-audio-dev@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=raymond.kk.lai@gmail.com \
    /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
all inboxes | Powered by JetHome®