From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Nils Faerber
<nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Interrupt routing problem
Date: Wed, 7 Jan 2004 16:34:51 +0100 [thread overview]
Message-ID: <20040107153451.GA31008@hell.org.pl> (raw)
In-Reply-To: <20040107090531.GA32086-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
Thus wrote Karol Kozimor:
> I remember Len writing about one, I'll dig up the old email and point you
> to the correct entry (basically, it was about not printing / taking into
> account default BIOS links settings under certain conditions).
Plese refer to:
http://bugme.osdl.org/show_bug.cgi?id=1320#c10
http://bugme.osdl.org/show_bug.cgi?id=430
#430 in particular doesn't seem to be fixed, i.e. both 2.4.23 and
2.6.0-rc1-mm1 don't seem to print IRQ#9 as available.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-07 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 8:50 Interrupt routing problem Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C83-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07 9:05 ` Karol Kozimor
[not found] ` <20040107090531.GA32086-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-07 15:34 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 4:14 Yu, Luming
2004-01-13 9:08 Yu, Luming
2004-01-13 8:50 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CC3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13 9:00 ` Karol Kozimor
[not found] ` <20040113090003.GB3599-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-15 10:41 ` Nils Faerber
2004-01-12 5:28 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CA9-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13 8:26 ` Karol Kozimor
2004-01-05 2:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C75-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-06 4:10 ` Len Brown
[not found] ` <1073362251.2419.21.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-06 8:47 ` Karol Kozimor
2004-01-04 16:43 Nils Faerber
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=20040107153451.GA31008@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.