From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: generic method to assign IRQs
Date: 14 Jun 2003 00:39:55 -0400 [thread overview]
Message-ID: <1055565595.3362.0.camel@aurora.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0306140035560.29854-100000@router.windsormachine.com>
On Sat, 2003-06-14 at 00:37, Mike Dresser wrote:
> Some of the problem is that motherboard manufacturers setup their hardware
> so that slots HAVE to share IRQ's no matter what you do. I've seen
> motherboards that have shared IRQ's even if there are no cards plugged in.
>
> Mike
Valid data point: Asus A7N8X motherboard. Then again, it does have
everything, including the sink.
Trever
--
"Blessed is the man, who having nothing to say, abstains from giving
wordy evidence of the fact." -- George Eliot
next prev parent reply other threads:[~2003-06-14 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 4:12 generic method to assign IRQs Florin Andrei
2003-06-14 4:37 ` Mike Dresser
2003-06-14 4:39 ` Trever L. Adams [this message]
2003-06-15 22:26 ` Florin Andrei
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=1055565595.3362.0.camel@aurora.localdomain \
--to=tadams-lists@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser_l@windsormachine.com \
/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;
as well as URLs for NNTP newsgroup(s).