mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Keith Chew" <keith.chew@gmail.com>
To: "Erik Mouw" <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IO APIC IRQ assignment
Date: Wed, 31 May 2006 02:05:44 +1200	[thread overview]
Message-ID: <20f65d530605300705l60bfcca7k47a41c95bf42a0ef@mail.gmail.com> (raw)
In-Reply-To: <20060530135017.GD5151@harddisk-recovery.com>

Hi Erik

> That sounds like a nice MythTV box to me :)
>

Yes it is! We are using the box as a video surveillance unit for the
automotive industry (eg trains, buses). We are using the USB for WIFI,
which is causing pain with the bttv drivers in IRQ sharing mode.
Increasing the PCI latency of the bttv allow it to not give up the IRQ
that often to the WIFI. The bttv FAQ did mention that the drivers
works "most of the time" in IRQ sharing, I guess we are seeing the
random freezes because our application is 24x7.

>
> Or the engineer means that in legacy PIC mode the IRQs are shared, but
> in APIC mode they can be separated. That is a different thing, cause in
> that case the IRQ lines are not physically connected, but put together
> in PIC mode and can again be separated by using APIC mode.
>

Ah, you could be right here. In the BIOS, there an option to
enable/disable APIC, which corresponds to what you are suggesting
above.

Unfortunately, we have tried all the options we know to separate the
IRQs in IO APIC mode, but to no avail. Next, we will be testing the
unit in Windows to verify the engineer's claims.

Thanks again for taking the time to respond to my post.

Regards
Keith

  reply	other threads:[~2006-05-30 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 12:21 Keith Chew
2006-05-30 12:31 ` James Courtier-Dutton
2006-05-30 13:26   ` Keith Chew
2006-05-30 13:50 ` Erik Mouw
2006-05-30 14:05   ` Keith Chew [this message]
2006-05-31 22:03     ` Jan Engelhardt
2006-05-31 23:12       ` Keith Chew
2006-06-01  9:42         ` Erik Mouw
2006-06-01 10:38           ` Keith Chew
2006-06-01 15:35             ` Keith Chew
2006-06-01 15:58               ` Thiago Galesi
2006-06-01 21:27                 ` Keith Chew

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=20f65d530605300705l60bfcca7k47a41c95bf42a0ef@mail.gmail.com \
    --to=keith.chew@gmail.com \
    --cc=erik@harddisk-recovery.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®