From: Pierre Ossman <drzeus-list@drzeus.cx>
To: krishna <krishna.c@globaledgesoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: problem between audio driver and mmc driver
Date: Thu, 03 Mar 2005 12:33:17 +0100 [thread overview]
Message-ID: <4226F5FD.1050304@drzeus.cx> (raw)
In-Reply-To: <4221E981.10004@globaledgesoft.com>
krishna wrote:
> Hi All,
>
> I have a strange problem.
> The Audio driver is statically compiled into the kernel.
>
> When I am loading my MMC driver, It is getting Audio Interrupts.
>
> I browsed thru the web and found out it is a bug in the hardware.
>
> The hardware bug is preventing Audio driver and MMC driver work
> simultaneously.
> Does any one have a solution Or a Work around to make both the drivers
> work though the audio driver
> is statically compiled into the kernel.
>
You should specify which hardware (audio and mmc) that is causing the
problem and also try to include the maintainers of each as cc.
Also, it's helpful if you can include links to the websites you've found
concerning the problem.
Rgds
Pierre
prev parent reply other threads:[~2005-03-03 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 15:38 problem between audio driver and mmc driver krishna
2005-03-03 11:33 ` Pierre Ossman [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=4226F5FD.1050304@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=krishna.c@globaledgesoft.com \
--cc=linux-kernel@vger.kernel.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