From: Takashi Iwai <tiwai@suse.de>
To: David Fries <dfries@mail.win.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] opl3sa2.c more detail on irq allocation fail
Date: Tue, 13 Jan 2004 18:16:31 +0100 [thread overview]
Message-ID: <s5hllobvkeo.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040110020823.GB2399@spacedout.fries.net>
Hi,
At Fri, 9 Jan 2004 20:08:23 -0600,
David Fries wrote:
>
> I need this patch so in the future if something is taking the irq and
> I don't notice it I'll at least have a message saying so.
>
> I tried the 2.4.22 kernel and all it would tell me was that the opl3sa
> module couldn't find the hardware. Finally I went back and added some
> printk messages to track down where the problem was. It turns out
> that acpi was allocating irq 5 to the pcmcia socket where 2.4.21 and
> before left that interrupt free. If I had a message like the one
> below I would have had something to look for. It turns out that
> 2.4.23 works fine, it just assigns all the pci devices to use irq 11,
> which works, but isn't optional.
thanks for the notice.
i added the error messages in each driver for the resource allocation
failures. please check the cvs tree later.
>
> Is this the right place to send patches?
yes.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
prev parent reply other threads:[~2004-01-13 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 2:08 [PATCH] opl3sa2.c more detail on irq allocation fail David Fries
2004-01-13 17:16 ` Takashi Iwai [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=s5hllobvkeo.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dfries@mail.win.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