public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: "'A list for linux audio users'" 
	<linux-audio-user@music.columbia.edu>,
	alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	linux-pcmcia@lists.infradead.org
Subject: Re: [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket
Date: Tue, 30 Mar 2004 09:00:53 +0100	[thread overview]
Message-ID: <20040330090053.A3956@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040330055204.UUGL2042.smtp1.fuse.net@64BitBadass>; from ico@fuse.net on Tue, Mar 30, 2004 at 12:52:11AM -0500

On Tue, Mar 30, 2004 at 12:52:11AM -0500, Ivica Ico Bukvic wrote:
> 6) Pester alsa-dev, lau, and kernel/pcmcia people to death begging for help
> :-)
> 
> IN-PROGRESS :-)

What needs to happen is that the card driver author needs to investigate
what is going on, and, if it seems related to the core PCMCIA core or
the socket driver, we need to get involved.

IOW, linux-pcmcia people don't debug card drivers.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-03-30  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040329235823.04bacef4@laptop>
2004-03-30  5:52 ` [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket Ivica Ico Bukvic
2004-03-30  8:00   ` Russell King [this message]
2004-03-30 19:15     ` Ivica Ico Bukvic

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=20040330090053.A3956@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ico@fuse.net \
    --cc=linux-audio-user@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.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