From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Annoying kernel behaviour
Date: 25 Jun 2001 07:41:56 GMT [thread overview]
Message-ID: <slrn9jdqq4.3af.kraxel@bytesex.org> (raw)
In-Reply-To: <3B33EFC0.D9C930D5@bigfoot.com> <9h0r6s$fe7$1@ns1.clouddancer.com> <20010623090542.6019D7846F@mail.clouddancer.com> <3B35C2FA.37F57964@bigfoot.com> <9h4ft5$1ku$1@ns1.clouddancer.com> <20010624114655.3D187784C4@mail.clouddancer.com> <3B3643A8.F3FE1E92@bigfoot.com> <9h5gbc$3mb$1@ns1.clouddancer.com> <20010625032231.930C8784C4@mail.clouddancer.com>
> >There are no conflicts, and PCI should be able to share anyways.
>
> That's the theory now for some time, has never worked. Even hacking
> the SCSI driver, any attempted IRQ sharing kills my systems. Even my
> quad ethernet is not successful at sharing IRQs with itself, in 2+ very
> different motherboards.
For bttv I know that irq sharing works in some cases and not on others.
Last not-working report was bttv sharing with a nvidia. Moving the
grabber board to another PCI slot (nvidia having a exclusive irq then,
bttv shared the irq with something else) fixed it.
Gerd
--
Damn lot people confuse usability and eye-candy.
prev parent reply other threads:[~2001-06-25 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 1:24 Annoying kernel behaviour Dylan Griffiths
[not found] ` <9h0r6s$fe7$1@ns1.clouddancer.com>
2001-06-23 9:05 ` Colonel
2001-06-24 10:37 ` Dylan Griffiths
[not found] ` <9h4ft5$1ku$1@ns1.clouddancer.com>
2001-06-24 11:46 ` Colonel
2001-06-24 19:46 ` Dylan Griffiths
[not found] ` <9h5gbc$3mb$1@ns1.clouddancer.com>
2001-06-25 3:22 ` Colonel
2001-06-25 7:41 ` Gerd Knorr [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=slrn9jdqq4.3af.kraxel@bytesex.org \
--to=kraxel@bytesex.org \
--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 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.