From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: "Pere Castañer" <XaRz69-pCzzcW6XgXY@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Acpi irq handler doesn't detect ICH4 sound device with ALSA. Is a known bug?
Date: Sun, 15 Aug 2004 13:35:42 -0400 [thread overview]
Message-ID: <411F9EEE.5070402@optonline.net> (raw)
In-Reply-To: <20040813232416.2119a446@debian>
Pere Castañer wrote:
>On Fri, 13 Aug 2004 15:25:09 -0400
>Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org> wrote:
>
>
>
>>Does "acpi=irq" also work? That is a little less aggressive about what
>>it disables...
>>
>>
>
>No. I've the same results of letting acpi to andle the irqs.
>Where I can find documentation of irq management in kernel? I don't know anything of the benefits of letting acpi to handle the irq and could be an interesting reading for a nerd computer student like me..
>
>Regards,
>
>
Oops! I meant to say "acpi=noirq"
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-15 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 19:16 Acpi irq handler doesn't detect ICH4 sound device with ALSA. Is a known bug? Pere Castañer
2004-08-13 19:25 ` Nathan Bryant
[not found] ` <411D1595.7090706-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-13 21:24 ` Pere Castañer
2004-08-15 17:35 ` Nathan Bryant [this message]
2004-08-16 15:16 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2004-08-11 22:56 Pere Castañer
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=411F9EEE.5070402@optonline.net \
--to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
--cc=XaRz69-pCzzcW6XgXY@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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